Triple
T6417955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6052 |
E127875
|
entity |
| Predicate | updates |
P4061
|
FINISHED |
| Object |
RFC 4291
RFC 4291 is the core Internet standard that defines the IPv6 addressing architecture, including address formats, allocation, and representation.
|
E593231
|
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 4291 | Statement: [RFC 6052, updates, RFC 4291]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4291 Context triple: [RFC 6052, updates, RFC 4291]
-
A.
RFC 4632
RFC 4632 is an Internet standards document that specifies the operational and technical details of Classless Inter-Domain Routing (CIDR) for efficient IP address allocation and routing on the Internet.
-
B.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
C.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
D.
RFC 4271
RFC 4271 is the core Internet standards document that specifies the Border Gateway Protocol version 4 (BGP-4), which governs inter-domain routing between autonomous systems.
-
E.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
- 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 4291 Triple: [RFC 6052, updates, RFC 4291]
Generated description
RFC 4291 is the core Internet standard that defines the IPv6 addressing architecture, including address formats, allocation, and representation.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4291 Target entity description: RFC 4291 is the core Internet standard that defines the IPv6 addressing architecture, including address formats, allocation, and representation.
-
A.
RFC 4632
RFC 4632 is an Internet standards document that specifies the operational and technical details of Classless Inter-Domain Routing (CIDR) for efficient IP address allocation and routing on the Internet.
-
B.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
C.
RFC 8200
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
D.
RFC 4271
RFC 4271 is the core Internet standards document that specifies the Border Gateway Protocol version 4 (BGP-4), which governs inter-domain routing between autonomous systems.
-
E.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068eb6c988190b54de6182d0f490d |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640d2ab64819089e91525da60392b |
completed | March 27, 2026, 8:33 a.m. |
| NEDg | Description generation | batch_69c644ec2ca48190997a118f8751cba5 |
completed | March 27, 2026, 8:50 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c6455961b881908f5804d9c0e86573 |
completed | March 27, 2026, 8:52 a.m. |
Created at: March 22, 2026, 4:42 p.m.