Triple
T1777475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1901 |
E39212
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
|
E222149
|
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 1452 | Statement: [RFC 1901, obsoletes, RFC 1452]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1452 Context triple: [RFC 1901, obsoletes, RFC 1452]
-
A.
RFC 1450
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
B.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
C.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
D.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- 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 1452 Triple: [RFC 1901, obsoletes, RFC 1452]
Generated description
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1452 Target entity description: RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
A.
RFC 1450
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
B.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
C.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
D.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa64b967f08190a73216361b9c2d83 |
completed | March 6, 2026, 5:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0305b6d08190804da5445e1f54d9 |
completed | March 8, 2026, 11:15 p.m. |
| NEDg | Description generation | batch_69ae03b41dcc81909b4439006bdffc64 |
completed | March 8, 2026, 11:18 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae044314188190a7472cf5f8e89f6c |
completed | March 8, 2026, 11:20 p.m. |
Created at: March 4, 2026, 7:31 p.m.