Triple
T8985573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1449 |
E214653
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 1908 |
E275764
|
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 1908 | Statement: [RFC 1449, obsoletedBy, RFC 1908]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1908 Context triple: [RFC 1449, obsoletedBy, RFC 1908]
-
A.
RFC 1908
chosen
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
B.
RFC 1889
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
-
C.
RFC 1108
RFC 1108 is an early Internet standards document that specifies security options for the Internet Protocol (IP), particularly for use in military and other high-security environments.
-
D.
RFC 1909
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
-
E.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67eddbf08190afca16e0be435241 |
completed | April 1, 2026, 12:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0475435808190a80d82b6614b1308 |
completed | April 3, 2026, 11:03 p.m. |
Created at: March 30, 2026, 7:03 p.m.