Triple
T2855589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinerama film process |
E63191
|
entity |
| Predicate | screenCurvature |
P43676
|
FINISHED |
| Object | approximately 146 degrees |
—
|
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: approximately 146 degrees | Statement: [Cinerama film process, screenCurvature, approximately 146 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenCurvature Context triple: [Cinerama film process, screenCurvature, approximately 146 degrees]
-
A.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
B.
screenDebut
Indicates the event or relationship in which an entity appears on screen for the first time in a film, television, or other visual media production.
-
C.
supportsWideColorGamut
Indicates that one entity provides or enables compatibility with a wide color gamut capability for another entity or context.
-
D.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
E.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
- 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_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. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 10:02 p.m.