Triple
T8723038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 877 |
E207057
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 1042 |
E325859
|
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 1042 | Statement: [RFC 877, obsoletedBy, RFC 1042]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1042 Context triple: [RFC 877, obsoletedBy, RFC 1042]
-
A.
RFC 1042
chosen
RFC 1042 is an early Internet standard that specifies how to encapsulate IP and ARP packets over IEEE 802 local area networks.
-
B.
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.
-
C.
RFC 1451
RFC 1451 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
D.
RFC 1442
RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
-
E.
RFC 1048
RFC 1048 is an Internet standards document that specifies the vendor information extensions for the BOOTP protocol, laying groundwork later used by DHCP.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0791208190b043332247372d7b |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf290001108190a90784b13a0a25b1 |
completed | April 3, 2026, 2:42 a.m. |
Created at: March 30, 2026, 6:36 p.m.