Triple

T1370766
Position Surface form Disambiguated ID Type / Status
Subject AFL Grand Final E30107 entity
Predicate formerOvertimeRule P27054 FINISHED
Object replay if scores were tied 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: replay if scores were tied | Statement: [AFL Grand Final, formerOvertimeRule, replay if scores were tied]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerOvertimeRule
Context triple: [AFL Grand Final, formerOvertimeRule, replay if scores were tied]
  • A. overtimeRule
    Indicates the rule or policy that defines when and how overtime work is calculated or applied.
  • B. overtimeFormatRegularSeason
    Indicates the format or rules used for overtime periods specifically during the regular season.
  • C. overtimePlayed
    Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
  • D. overtimeFormatPlayoffs
    Indicates that the relationship or action pertains to the specific overtime rules or structure used during playoff games, as distinct from regular-season overtime formats.
  • E. formerEligibilityRule
    Indicates that an entity was previously subject to a particular eligibility rule, but that rule no longer currently applies.
  • 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_69a498f912008190a376a98b207b2071 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c2d7b6008190bc0303b56959ba56 completed March 1, 2026, 10:51 p.m.
PD Predicate disambiguation batch_69a4befb08b88190be966fa1aadd4bcd completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4bfc2134c81909cbaaa151d96e9a8 completed March 1, 2026, 10:37 p.m.
Created at: March 1, 2026, 7:57 p.m.