Triple

T17422372
Position Surface form Disambiguated ID Type / Status
Subject 2012 NHL All-Star Game E423646 entity
Predicate reasonNextNotHeld P127398 FINISHED
Object 2012–13 NHL lockout 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: 2012–13 NHL lockout | Statement: [2012 NHL All-Star Game, reasonNextNotHeld, 2012–13 NHL lockout]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonNextNotHeld
Context triple: [2012 NHL All-Star Game, reasonNextNotHeld, 2012–13 NHL lockout]
  • A. notAutomaticallyHeldBy
    Indicates that a particular right, status, or condition is not granted or possessed by default and must be explicitly obtained or established.
  • B. notHeldIn
    Indicates that an event, activity, or state does not take place or is not located within a specified context, location, or time frame.
  • C. reasonNotHeldPreviousYear
    Indicates that there was a specific reason why something did not take place or was not held in the previous year.
  • D. notHeldDuring
    Indicates that a specified condition, event, or relationship does not occur or is not in effect throughout a given time interval or temporal context.
  • E. cannotBeHeldBy
    Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
  • 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44237f2cc819083ca0e7e00d828fb completed April 19, 2026, 2:47 a.m.
PD Predicate disambiguation batch_69e3b02e6cc88190986e85e64ce9383e completed April 18, 2026, 4:24 p.m.
PDg Predicate description generation batch_69e3b2a33e8481908fa6ef45290d08aa completed April 18, 2026, 4:34 p.m.
Created at: April 10, 2026, 5:46 a.m.