Triple
T2855595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinerama film process |
E63191
|
entity |
| Predicate | projectionFilmGauge |
P21733
|
FINISHED |
| Object | 35 mm |
—
|
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: 35 mm | Statement: [Cinerama film process, projectionFilmGauge, 35 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectionFilmGauge Context triple: [Cinerama film process, projectionFilmGauge, 35 mm]
-
A.
filmGauge
chosen
Indicates the specific width or size of the film stock used in a motion picture or photographic recording.
-
B.
projectionFormat
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
C.
studioSystemFilm
Indicates that a film was produced, distributed, or otherwise created under the control or framework of a particular studio system.
-
D.
distributedFilm
Indicates that one entity served as the distributor responsible for releasing or circulating a particular film.
-
E.
filmSettingTheater
Indicates that a film’s setting or key scenes take place in a theater (such as a cinema or playhouse).
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf62308081908a65decdd5d6f918 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.