Triple
T27582825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Address Book |
E699624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | directory database |
C14788
|
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: directory database Context triple: [Public Address Book, instanceOf, directory database]
-
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.
database
chosen
A database is an organized collection of structured or unstructured data stored and managed in a way that enables efficient retrieval, modification, and administration.
-
C.
public domain database
A public domain database is a structured collection of data whose contents are free from intellectual property restrictions, allowing anyone to use, modify, and distribute the data without permission or payment.
-
D.
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.
-
E.
bibliographic database
A bibliographic database is a structured collection of references to published literature, such as books, articles, and reports, organized to support efficient search, retrieval, and management of bibliographic information.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:03 p.m.