Triple
T2114357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDAP |
E42572
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 4518
RFC 4518 is an Internet standard that specifies string preparation and comparison rules for use in LDAP directories.
|
E241870
|
NE FINISHED |
How this triple was built (4 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: RFC 4518 | Statement: [LDAP, definedInRFC, RFC 4518]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4518 Context triple: [LDAP, definedInRFC, RFC 4518]
-
A.
RFC 4513
RFC 4513 is an IETF standard that specifies authentication methods and security mechanisms for the Lightweight Directory Access Protocol (LDAP).
-
B.
RFC 4514
RFC 4514 is an IETF standard that specifies the string representation of Distinguished Names in the Lightweight Directory Access Protocol (LDAP).
-
C.
RFC 4510
RFC 4510 is an IETF standards-track document that specifies the core technical framework and protocol suite for the Lightweight Directory Access Protocol (LDAP).
-
D.
RFC 4517
RFC 4517 is an Internet standard that specifies the syntaxes and matching rules used in the Lightweight Directory Access Protocol (LDAP).
-
E.
RFC 4512
RFC 4512 is an IETF specification that defines the core models, schema, and protocol elements for the Lightweight Directory Access Protocol (LDAP) version 3.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 4518 Triple: [LDAP, definedInRFC, RFC 4518]
Generated description
RFC 4518 is an Internet standard that specifies string preparation and comparison rules for use in LDAP directories.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4518 Target entity description: RFC 4518 is an Internet standard that specifies string preparation and comparison rules for use in LDAP directories.
-
A.
RFC 4513
RFC 4513 is an IETF standard that specifies authentication methods and security mechanisms for the Lightweight Directory Access Protocol (LDAP).
-
B.
RFC 4514
RFC 4514 is an IETF standard that specifies the string representation of Distinguished Names in the Lightweight Directory Access Protocol (LDAP).
-
C.
RFC 4510
RFC 4510 is an IETF standards-track document that specifies the core technical framework and protocol suite for the Lightweight Directory Access Protocol (LDAP).
-
D.
RFC 4517
RFC 4517 is an Internet standard that specifies the syntaxes and matching rules used in the Lightweight Directory Access Protocol (LDAP).
-
E.
RFC 4512
RFC 4512 is an IETF specification that defines the core models, schema, and protocol elements for the Lightweight Directory Access Protocol (LDAP) version 3.
- F. None of above. chosen
Provenance (5 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5d8bffd0819095629956f9584222 |
completed | March 9, 2026, 5:41 a.m. |
| NEDg | Description generation | batch_69ae5e48eefc8190b459278860bb3217 |
completed | March 9, 2026, 5:44 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae5ec233788190a52dc1a135f7dfb9 |
completed | March 9, 2026, 5:46 a.m. |
Created at: March 4, 2026, 7:43 p.m.