Triple

T19519738
Position Surface form Disambiguated ID Type / Status
Subject Maurice Richard striking linesman Cliff Thompson E488371 entity
Predicate officiatingRoleOfCliffThompson P93909 FINISHED
Object linesman 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: linesman | Statement: [Maurice Richard striking linesman Cliff Thompson, officiatingRoleOfCliffThompson, linesman]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: officiatingRoleOfCliffThompson
Context triple: [Maurice Richard striking linesman Cliff Thompson, officiatingRoleOfCliffThompson, linesman]
  • A. umpireCrewRole
    Indicates the specific role or position an umpire holds within an umpire crew during an event or game.
  • B. typeOfUmpire chosen
    Indicates the specific category or role an umpire belongs to within the broader set of umpires.
  • C. eraAsUmpire
    Indicates the time period during which an entity served in the role of an umpire.
  • D. hasCourtOfficial
    Indicates that an entity is associated with, employs, or is served by a court official in an official capacity.
  • E. hasOfficiatingCrew
    Indicates that an event, typically a sports game or formal proceeding, is assigned a specific group of officials responsible for overseeing and enforcing its rules.
  • 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_69d8e8da8bec819081f400199491ccc3 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6359feb808190ba94563831adc720 completed April 20, 2026, 2:18 p.m.
PD Predicate disambiguation batch_69e4fd7d0da88190aabf8b5799691fb1 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:40 p.m.