Triple
T18564609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3490 |
E453730
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 5893 |
—
|
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 5893 | Statement: [RFC 3490, obsoletedBy, RFC 5893]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5893 Context triple: [RFC 3490, obsoletedBy, RFC 5893]
-
A.
RFC 5639
RFC 5639 is an IETF standard document that specifies the Brainpool family of elliptic curves for use in cryptographic applications.
-
B.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
C.
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).
-
D.
RFC 5892
chosen
RFC 5892 is an IETF standard that defines the rules for allowable Unicode code points in Internationalized Domain Names (IDNs) under the IDNA2008 framework.
-
E.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
Created at: April 10, 2026, 11:42 a.m.