Triple
T8791618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5661 |
E209178
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 3530 |
E213343
|
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 3530 | Statement: [RFC 5661, obsoletes, RFC 3530]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3530 Context triple: [RFC 5661, obsoletes, RFC 3530]
-
A.
RFC 3530
chosen
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
B.
RFC 3610
RFC 3610 is an IETF specification that defines the Counter with CBC-MAC (CCM) mode of operation for cryptographic block ciphers, commonly used for providing authenticated encryption in network protocols such as Wi-Fi security (CCMP).
-
C.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8e6e4881909155c40c52bc082c |
completed | March 31, 2026, 11:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6f493f648190b0e9392f1abb44a1 |
completed | April 3, 2026, 7:42 a.m. |
Created at: March 30, 2026, 6:43 p.m.