Triple
T5421650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 760 |
E121263
|
entity |
| Predicate | hasSection |
P35
|
FINISHED |
| Object | Internet Datagram Header Format |
E9801
|
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: Internet Datagram Header Format | Statement: [RFC 760, hasSection, Internet Datagram Header Format]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Internet Datagram Header Format Context triple: [RFC 760, hasSection, Internet Datagram Header Format]
-
A.
RFC 791
chosen
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
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 793
RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
-
D.
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.
-
E.
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.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87eac41481908a4982db5d119edd |
completed | March 20, 2026, 5:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf487db2bc81908822d3adadaff0dd |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:06 p.m.