Triple
T10158300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4516 |
E233825
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | LDAPv3 |
E827891
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: LDAPv3 | Statement: [RFC 4516, relatedTo, LDAPv3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LDAPv3 Context triple: [RFC 4516, relatedTo, LDAPv3]
-
A.
LDAP
LDAP (Lightweight Directory Access Protocol) is an open, standards-based protocol used to access and manage distributed directory information services over an IP network.
-
B.
Lightweight Directory Access Protocol
chosen
Lightweight Directory Access Protocol (LDAP) is an open, standards-based application protocol used to access and manage distributed directory information services over an IP network.
-
C.
OpenLDAP
OpenLDAP is a widely used open-source implementation of the Lightweight Directory Access Protocol, providing directory services for authentication, authorization, and centralized user management.
-
D.
ldapcompare
ldapcompare is an OpenLDAP command-line utility used to compare attribute values of directory entries against specified values in an LDAP directory.
-
E.
X.500
X.500 is an ITU-T and ISO/IEC standard series that defines a directory service model and protocols for distributed, hierarchical storage and retrieval of information about networked entities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3176ac9388190bc76b3cffce93a3d |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:09 p.m.