Triple
T22166216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WXTV-DT |
E547794
|
entity |
| Predicate | transitionedFromAnalogToDigital |
P147229
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WXTV-DT, transitionedFromAnalogToDigital, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedFromAnalogToDigital Context triple: [WXTV-DT, transitionedFromAnalogToDigital, yes]
-
A.
switchedToDigitalOnly
Indicates that an entity has transitioned from offering physical or hybrid formats to providing only digital versions of its product or service.
-
B.
isAnalogOrDigital
Indicates whether something operates using analog signals/representation or digital signals/representation.
-
C.
usedAsAnalogFor
Indicates that one entity is employed as a comparison or illustrative counterpart to help explain, represent, or understand another entity.
-
D.
hasAnalog
Indicates that one entity corresponds to or functions similarly to another entity in a comparable context or role.
-
E.
digitalTransitionDate
Indicates the date on which something changes from an analog or traditional form to a digital form or system.
- F. None of above. chosen
Provenance (4 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a314cc081908857c13d018d52b2 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:34 p.m.