Triple
T6417954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6052 |
E127875
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2766 |
E545175
|
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 2766 | Statement: [RFC 6052, obsoletes, RFC 2766]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2766 Context triple: [RFC 6052, obsoletes, RFC 2766]
-
A.
RFC 2766
chosen
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.
-
B.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
C.
RFC 2467
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.
-
D.
RFC 1666
RFC 1666 is an early Internet standards document that was later superseded by RFC 1901 as the protocol or specification it defined evolved.
-
E.
RFC 1667
RFC 1667 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068eb6c988190b54de6182d0f490d |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640d2ab64819089e91525da60392b |
completed | March 27, 2026, 8:33 a.m. |
Created at: March 22, 2026, 4:42 p.m.