Triple
T21802393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2778 |
—
|
NE NERFINISHED |
How this triple was built (3 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 2778 | Statement: [RFC 4632, obsoletes, RFC 2778]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2778 Context triple: [RFC 4632, obsoletes, RFC 2778]
-
A.
RFC 2776
RFC 2776 was an early Internet standards document that specified the IPv6 Router Alert Option, later refined and replaced by RFC 4632.
-
B.
RFC 2770
RFC 2770 is an Internet Engineering Task Force (IETF) document that originally specified experimental IPv4 address allocation practices before being superseded by later standards.
-
C.
RFC 2774
RFC 2774 is an Internet Engineering Task Force (IETF) document that originally specified an HTTP Extension Framework, later superseded by RFC 4632.
-
D.
RFC 2773
RFC 2773 is an older Internet Engineering Task Force (IETF) document that specified an earlier approach to IP addressing and routing, later superseded by RFC 4632.
-
E.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2778 Target entity description: RFC 2778 is an Internet standards-track document that defines a model for presence and instant messaging, laying foundational concepts later refined by subsequent protocols.
-
A.
RFC 2776
RFC 2776 was an early Internet standards document that specified the IPv6 Router Alert Option, later refined and replaced by RFC 4632.
-
B.
RFC 2770
RFC 2770 is an Internet Engineering Task Force (IETF) document that originally specified experimental IPv4 address allocation practices before being superseded by later standards.
-
C.
RFC 2774
RFC 2774 is an Internet Engineering Task Force (IETF) document that originally specified an HTTP Extension Framework, later superseded by RFC 4632.
-
D.
RFC 2773
RFC 2773 is an older Internet Engineering Task Force (IETF) document that specified an earlier approach to IP addressing and routing, later superseded by RFC 4632.
-
E.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
- F. None of above. chosen
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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
Created at: April 16, 2026, 6:53 p.m.