Triple
T8530331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 870 |
E201928
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 1010 |
E325858
|
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 1010 | Statement: [RFC 870, obsoletedBy, RFC 1010]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1010 Context triple: [RFC 870, obsoletedBy, RFC 1010]
-
A.
RFC 1010
chosen
RFC 1010 was an early Internet standards document that provided an official list of assigned protocol numbers and related parameters before being superseded by later updates.
-
B.
RFC 1910
RFC 1910 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
RFC 1012
RFC 1012 is an early Internet standards document that specified requirements and guidelines for host communication protocols before being superseded by later updates.
-
D.
RFC 1031
RFC 1031 is an early Internet standards document that specified guidelines for the implementation and operation of certain TCP/IP networking protocols before being superseded by later updates.
-
E.
RFC 1013
RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe67546248190b359c845c0161ad3 |
completed | March 31, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6d68d14c81908bde8ca0113f9503 |
completed | April 2, 2026, 1:21 p.m. |
Created at: March 30, 2026, 6:17 p.m.