Triple

T32173537
Position Surface form Disambiguated ID Type / Status
Subject Dolby 3D E821772 entity
Predicate screenRequirement P29568 FINISHED
Object standard white projection screen 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: standard white projection screen | Statement: [Dolby 3D, screenRequirement, standard white projection screen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: screenRequirement
Context triple: [Dolby 3D, screenRequirement, standard white projection screen]
  • A. platformRequirement chosen
    Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
  • B. screenCapacity
    Indicates the maximum number of items or content units that can be displayed on a screen at one time.
  • C. requiresDevice
    Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
  • D. winRequirement
    Indicates that one entity specifies a condition or set of conditions that must be satisfied for another entity to achieve a win or success.
  • E. resolutionRequires
    Indicates that resolving one issue, task, or condition depends on first completing or satisfying another specified prerequisite.
  • 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_69f3490699a48190bbef96b198e8fade completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 12:33 a.m.