Triple
T10623832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7127 |
E250270
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2026 |
E250269
|
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 2026 | Statement: [RFC 7127, obsoletes, RFC 2026]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2026 Context triple: [RFC 7127, obsoletes, RFC 2026]
-
A.
RFC 2026
chosen
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
B.
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.
-
C.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
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 2156
RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7f11fc8190aed858f2e1443c08 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96b9a27f881908e451bfa6c118af4 |
completed | April 10, 2026, 9:28 p.m. |
Created at: April 8, 2026, 8:52 p.m.