Triple
T10792443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1664 |
E254614
|
entity |
| Predicate | obsolete |
P41617
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [RFC 1664, obsolete, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsolete Context triple: [RFC 1664, obsolete, true]
-
A.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
-
B.
obsoletedStandard
Indicates that one standard has been rendered obsolete or superseded by another standard.
-
C.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
D.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
E.
defunct
chosen
Indicates that an entity has ceased to exist, operate, or function and is no longer active or in use.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f7ad408190af4727dd9d459498 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.