Triple
T10158244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4512 |
E233824
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2251 |
E845096
|
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: RFC 2251 | Statement: [RFC 4512, obsoletes, RFC 2251]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2251 Context triple: [RFC 4512, obsoletes, RFC 2251]
-
A.
RFC 2251
chosen
RFC 2251 is an Internet standard that originally specified the version 3 protocol for the Lightweight Directory Access Protocol (LDAPv3) before being superseded by later LDAP specifications.
-
B.
RFC 2252
RFC 2252 is an earlier LDAP specification that defines attribute syntax and matching rules, later revised and superseded by RFC 4517.
-
C.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
D.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
E.
RFC 2255
RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
- 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_69d32ac043f08190ba7f526d226d3c8c |
completed | April 6, 2026, 3:38 a.m. |
Created at: March 30, 2026, 9:09 p.m.