Triple
T32114196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Dynamic Digital Sound |
E820193
|
entity |
| Predicate | replacedAnalogFormat |
P28535
|
FINISHED |
| Object | optical analog soundtracks on film |
—
|
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: optical analog soundtracks on film | Statement: [Sony Dynamic Digital Sound, replacedAnalogFormat, optical analog soundtracks on film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAnalogFormat Context triple: [Sony Dynamic Digital Sound, replacedAnalogFormat, optical analog soundtracks on film]
-
A.
transitionedFromAnalogToDigital
Indicates that an entity changed its state, system, or format from analog to digital.
-
B.
formerAnalogChannel
Indicates that an entity was previously an analog channel but no longer holds that status.
-
C.
usedAsAnalogFor
Indicates that one entity is employed as a comparison or illustrative counterpart to help explain, represent, or understand another entity.
-
D.
replacedStandard
chosen
Indicates that one standard has been superseded or taken the place of another standard.
-
E.
createdFormatThatBecame
Indicates that one entity created a format which later evolved into or was adopted as another specified format.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 12:28 a.m.