Triple
T8009159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4033 |
E186439
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 3008
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
|
E707272
|
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 3008 | Statement: [RFC 4033, obsoletes, RFC 3008]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3008 Context triple: [RFC 4033, obsoletes, RFC 3008]
-
A.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
B.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
C.
RFC 3168
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
D.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
E.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
- 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 3008 Triple: [RFC 4033, obsoletes, RFC 3008]
Generated description
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3008 Target entity description: RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
-
A.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
B.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
C.
RFC 3168
RFC 3168 is an IETF standard that specifies the addition of Explicit Congestion Notification (ECN) to IP and TCP to enable end-to-end congestion signaling without relying solely on packet loss.
-
D.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
E.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d6f76408190a1312369521a187a |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc569e90d48190a1bf1495496017f8 |
completed | March 31, 2026, 11:19 p.m. |
| NEDg | Description generation | batch_69cc58a8f3d08190bec84dc1ba3b5b84 |
completed | March 31, 2026, 11:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cc5cb791b48190bd5004b518d23f84 |
completed | March 31, 2026, 11:45 p.m. |
Created at: March 30, 2026, 5:19 p.m.