Triple
T20907237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2866 |
E514833
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 5080 |
—
|
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 5080 | Statement: [RFC 2866, obsoletedBy, RFC 5080]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5080 Context triple: [RFC 2866, obsoletedBy, RFC 5080]
-
A.
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.
-
B.
RFC 5890
RFC 5890 is an Internet Engineering Task Force (IETF) standard that defines the terminology and concepts for Internationalized Domain Names (IDNs) in the Domain Name System (DNS).
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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 5080 Target entity description: RFC 5080 is an IETF standards-track document that provides clarifications and implementation guidelines for the Remote Authentication Dial-In User Service (RADIUS) protocol and related extensions.
-
A.
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.
-
B.
RFC 5890
RFC 5890 is an Internet Engineering Task Force (IETF) standard that defines the terminology and concepts for Internationalized Domain Names (IDNs) in the Domain Name System (DNS).
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e900ee7881909ab1046b40dca486 |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.