Triple

T29015202
Position Surface form Disambiguated ID Type / Status
Subject Alexander: Director's Cut E737282 entity
Predicate hasAlteredPacingComparedTo P107929 FINISHED
Object Alexander (theatrical cut) 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: Alexander (theatrical cut) | Statement: [Alexander: Director's Cut, hasAlteredPacingComparedTo, Alexander (theatrical cut)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlteredPacingComparedTo
Context triple: [Alexander: Director's Cut, hasAlteredPacingComparedTo, Alexander (theatrical cut)]
  • A. hasTempoChanges
    Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
  • B. isFastPaced
    Indicates that an activity, event, or process proceeds quickly with rapid progression and little downtime.
  • C. hasPaceGroups
    Indicates that an event or activity is organized into distinct groups based on participants’ pace or speed.
  • D. hasTempoVariety chosen
    Indicates that an entity exhibits variation or changes in tempo rather than maintaining a constant speed.
  • E. hasAlterationPeriod
    Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
  • 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_69f077ee19f881909af48f9cab00a2e5 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 28, 2026, 9:45 a.m.