Triple
T6422500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Case sound-on-film system |
E127976
|
entity |
| Predicate | soundReproductionType |
P3514
|
FINISHED |
| Object | optical sound |
—
|
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 sound | Statement: [Case sound-on-film system, soundReproductionType, optical sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundReproductionType Context triple: [Case sound-on-film system, soundReproductionType, optical sound]
-
A.
soundReproductionMethod
chosen
Indicates the method or technique used to reproduce or play back sound.
-
B.
soundHardware
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
C.
phonographicType
Indicates the specific kind or category of phonographic recording or medium associated with an entity.
-
D.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
E.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by another entity.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690576c48190b5db5464eacc9de3 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.