Triple
T21091781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Protocol type of service field |
E519654
|
entity |
| Predicate | redefinedBy |
P9775
|
FINISHED |
| Object | RFC 2474 |
—
|
NE NERFINISHED |
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 2474 | Statement: [Internet Protocol type of service field, redefinedBy, RFC 2474]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2474 Context triple: [Internet Protocol type of service field, redefinedBy, RFC 2474]
-
A.
RFC 2474
chosen
RFC 2474 is an IETF standard that defines the Differentiated Services (DiffServ) field in the IPv4 and IPv6 headers to support scalable quality-of-service (QoS) in IP networks.
-
B.
RFC 2464
RFC 2464 is an Internet standard that specifies how IPv6 packets are transmitted over Ethernet networks.
-
C.
RFC 2451
RFC 2451 is an Internet Engineering Task Force (IETF) standard that specifies how to use the Twofish encryption algorithm within the IPsec protocol suite for secure network communications.
-
D.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
E.
RFC 4303
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:51 p.m.