Triple
T10158212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4510 |
E233823
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | LDAPv3 specification |
E826108
|
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 specification | Statement: [RFC 4510, partOf, LDAPv3 specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LDAPv3 specification Context triple: [RFC 4510, partOf, LDAPv3 specification]
-
A.
RFC 4519
RFC 4519 is an IETF specification that defines a standard set of schema attributes and object classes for use in LDAP directories.
-
B.
Lightweight Directory Access Protocol
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.
RFC 4513
RFC 4513 is an IETF standard that specifies authentication methods and security mechanisms for the Lightweight Directory Access Protocol (LDAP).
-
D.
RFC 4511
chosen
RFC 4511 is an IETF standard that specifies the Lightweight Directory Access Protocol (LDAP) version 3, defining how directory services are accessed and managed over a network.
-
E.
RFC 2253
RFC 2253 is an Internet standard that originally defined the textual representation of LDAP distinguished names, later superseded by RFC 4514.
- 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_69d300acae608190891d8f55c3d5102b |
completed | April 6, 2026, 12:39 a.m. |
Created at: March 30, 2026, 9:09 p.m.