Triple
T32539563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADSI Edit |
E831678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LDAP editor |
C58662
|
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: LDAP editor Context triple: [ADSI Edit, instanceOf, LDAP editor]
-
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
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 schema element
An LDAP schema element is a defined component (such as an attribute type, object class, or matching rule) that specifies the structure, constraints, and semantics of data stored in an LDAP directory.
-
D.
LDAP specification
The LDAP specification defines a standardized protocol and data model for accessing, querying, and managing directory information services over a network.
-
E.
directory management service
A directory management service is a system that centrally maintains, organizes, and controls access to identity and resource information (such as users, groups, devices, and permissions) across an organization’s IT environment.
- F. None of above. chosen
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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.