Triple

T24564646
Position Surface form Disambiguated ID Type / Status
Subject 2005 British & Irish Lions tour to New Zealand E607747 entity
Predicate O’DriscollInjuryMatch P14288 FINISHED
Object first Test in Christchurch 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: first Test in Christchurch | Statement: [2005 British & Irish Lions tour to New Zealand, O’DriscollInjuryMatch, first Test in Christchurch]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: O’DriscollInjuryMatch
Context triple: [2005 British & Irish Lions tour to New Zealand, O’DriscollInjuryMatch, first Test in Christchurch]
  • A. injuryOpponentTeam
    Indicates that one team causes an injury to a member of the opposing team during a contest or interaction.
  • B. injuredIn
    Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
  • C. injuryInvolvedPlayer chosen
    Indicates that a specific player is involved in, affected by, or associated with a particular injury event.
  • D. battedAgainstTeamAtTimeOfInjury
    Indicates that a player batted against a specific team at the time when the player sustained an injury.
  • E. battedForTeamAtTimeOfInjury
    Indicates that a player was batting for a specific team at the time the injury occurred.
  • 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_69e2c4cc35a48190990b7571bc086df8 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f9d0f881909afc04537c32f76b completed April 30, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69f2a6b99e7c8190ba7e2dc8729a314a completed April 30, 2026, 12:47 a.m.
Created at: April 18, 2026, 2:28 a.m.