Triple

T16960861
Position Surface form Disambiguated ID Type / Status
Subject Copa América 1957 matches E411422 entity
Predicate usesOffsideRule P72177 FINISHED
Object yes 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: yes | Statement: [Copa América 1957 matches, usesOffsideRule, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesOffsideRule
Context triple: [Copa América 1957 matches, usesOffsideRule, yes]
  • A. offsideApplies chosen
    Indicates that an offside rule or condition is in effect and must be applied to the situation or event.
  • B. usesAwayGoalsRule
    Indicates that a competition or match outcome is decided using the away goals rule, where goals scored by a team in away games serve as a tiebreaker.
  • C. fifaEligibilityRule
    Indicates that a person meets the official criteria set by FIFA to represent a particular national team in international football competitions.
  • D. usesLimitedOversRules
    Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
  • E. goldenGoalRuleUsed
    Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
  • 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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0209a9081909d9c62456bc16e14 completed April 18, 2026, 6:40 p.m.
PD Predicate disambiguation batch_69e32b9cddf88190bc42709604047353 completed April 18, 2026, 6:58 a.m.
Created at: April 10, 2026, 5:31 a.m.