Triple
T16465649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6557 |
E399925
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2467 |
E167594
|
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: RFC 2467 | Statement: [RFC 6557, obsoletes, RFC 2467]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2467 Context triple: [RFC 6557, obsoletes, RFC 2467]
-
A.
RFC 2467
chosen
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
B.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
C.
RFC 2447
RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
-
D.
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.
-
E.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d841f348190958a25f35034edff |
completed | April 18, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f575ed48190a24d6af74565189d |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:11 a.m.