Triple
T21191080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4303 |
E522211
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2406 |
—
|
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 2406 | Statement: [RFC 4303, obsoletes, RFC 2406]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2406 Context triple: [RFC 4303, obsoletes, RFC 2406]
-
A.
RFC 2406
chosen
RFC 2406 is an Internet standards document that originally specified the Encapsulating Security Payload (ESP) protocol for providing confidentiality, authentication, and integrity in IPsec.
-
B.
RFC 2402
RFC 2402 is an Internet standards document that defines the IP Authentication Header (AH) protocol used to provide connectionless integrity, data origin authentication, and optional anti-replay protection for IP packets.
-
C.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
D.
RFC 1662
RFC 1662 is an Internet Engineering Task Force (IETF) standard that specifies the framing for Point-to-Point Protocol (PPP) over synchronous and asynchronous serial links.
-
E.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.