Triple
T15999564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GD-ROM |
E388059
|
entity |
| Predicate | obsolescenceStatus |
P48589
|
FINISHED |
| Object | discontinued |
—
|
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: discontinued | Statement: [GD-ROM, obsolescenceStatus, discontinued]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obsolescenceStatus Context triple: [GD-ROM, obsolescenceStatus, discontinued]
-
A.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
-
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.
specificationStatus
Indicates the current approval or completion state of a specification within its lifecycle (e.g., draft, under review, finalized).
-
E.
decommissioningStatus
chosen
Indicates the current phase or condition of an entity in the process of being taken out of active service or 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.