Triple
T22062083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7503 |
E545177
|
entity |
| Predicate | obsoletesSpecification |
P82887
|
FINISHED |
| Object | OSPFv3 specification in RFC 5340 |
—
|
LITERAL 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: OSPFv3 specification in RFC 5340 | Statement: [RFC 7503, obsoletesSpecification, OSPFv3 specification in RFC 5340]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsoletesSpecification Context triple: [RFC 7503, obsoletesSpecification, OSPFv3 specification in RFC 5340]
-
A.
supersededSpecificationIn
chosen
Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
-
B.
isObsoleteFor
Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
-
C.
becameObsoleteWhen
Indicates that one thing lost its relevance, usefulness, or validity at the time another specified event, condition, or entity came into existence or took effect.
-
D.
obsoletedStandard
Indicates that one standard has been rendered obsolete or superseded by another standard.
-
E.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
- F. None of above.
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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285e8c688190b701e417893cc148 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.