Triple
T10020031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java Naming and Directory Interface |
E200589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naming and directory service API |
C27294
|
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: naming and directory service API Context triple: [Java Naming and Directory Interface, instanceOf, naming and directory service API]
-
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 specification
The LDAP specification defines a standardized protocol and data model for accessing, querying, and managing directory information services over a network.
-
C.
virtual directory server
A virtual directory server is a middleware service that aggregates and presents data from multiple underlying directory and identity sources as a single, unified directory view without duplicating the data.
-
D.
authoritative name server
An authoritative name server is a DNS server that provides definitive, original answers for specific domain names based on data it directly manages, rather than relying on cached or forwarded information.
-
E.
network information service
A network information service is a system that centrally stores, manages, and distributes configuration and directory data (such as user accounts, hostnames, and services) across computers in a network.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 8:53 p.m.