Triple
T12165268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Panavision 70 |
E289817
|
entity |
| Predicate | soundFormatOn70mmPrint |
P27606
|
FINISHED |
| Object | 6‑track magnetic 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: 6‑track magnetic sound | Statement: [Super Panavision 70, soundFormatOn70mmPrint, 6‑track magnetic sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundFormatOn70mmPrint Context triple: [Super Panavision 70, soundFormatOn70mmPrint, 6‑track magnetic sound]
-
A.
usesFilmFormat
Indicates that one entity employs or is recorded in a particular film format associated with the other entity.
-
B.
isSoundFilm
Indicates that a film includes synchronized recorded sound as an integral part of its presentation, rather than being a silent film.
-
C.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
D.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
E.
phonographicType
chosen
Indicates the specific kind or category of phonographic recording or medium associated with an 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.