Triple
T28023617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organizational Unit |
E707752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Active Directory object class |
C27508
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Active Directory object class Context triple: [Organizational Unit, instanceOf, Active Directory object class]
-
A.
LDAP directory
An LDAP directory is a specialized, hierarchical database optimized for fast read access that stores and organizes information about users, groups, devices, and other network resources for authentication and authorization purposes.
-
B.
LDAP implementation
chosen
An LDAP implementation is a software component or system that provides directory services by storing, organizing, and enabling query and modification of hierarchical information using the Lightweight Directory Access Protocol.
-
C.
LDAP specification
The LDAP specification defines a standardized protocol and data model for accessing, querying, and managing directory information services over a network.
-
D.
proper class
A proper class is a collection of mathematical objects too large to be a set, such as the class of all sets or all ordinals, and therefore cannot be an element of any other collection.
-
E.
active object
An active object is a concurrent programming construct that encapsulates its own thread of control and processes method calls asynchronously, decoupling method invocation from execution.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:11 p.m.