Triple
T20907236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2866 |
E514833
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 2869 |
—
|
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 2869 | Statement: [RFC 2866, obsoletedBy, RFC 2869]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2869 Context triple: [RFC 2866, obsoletedBy, RFC 2869]
-
A.
RFC 2829
RFC 2829 is an earlier IETF standard that specified authentication methods and security mechanisms for LDAPv3 directory access before being superseded by later updates.
-
B.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
C.
RFC 2866
chosen
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.
-
D.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
-
E.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
- 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_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.