Triple
T22334476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5302 |
E552106
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 5308 |
—
|
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 5308 | Statement: [RFC 5302, obsoletedBy, RFC 5308]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5308 Context triple: [RFC 5302, obsoletedBy, RFC 5308]
-
A.
RFC 5308
chosen
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
B.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
-
C.
RFC 3008
RFC 3008 is an earlier Internet Engineering Task Force (IETF) standards document related to DNS security that was later superseded by RFC 4033.
-
D.
RFC 5780
RFC 5780 is an IETF standard that extends the STUN protocol to help diagnose and characterize NAT and firewall behavior for improved NAT traversal.
-
E.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577e35f48190b11789d80182653e |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:43 p.m.