Triple

T5083528
Position Surface form Disambiguated ID Type / Status
Subject Los Angeles Angels–Texas Rangers rivalry E114579 entity
Predicate isDivisionalFeud P903 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: [Los Angeles Angels–Texas Rangers rivalry, isDivisionalFeud, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isDivisionalFeud
Context triple: [Los Angeles Angels–Texas Rangers rivalry, isDivisionalFeud, yes]
  • A. divisionIChampionship
    Indicates that an entity has won or holds a Division I championship title in a given sport or competition.
  • B. divisionRivalry chosen
    Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
  • C. isDivisionalMatchup
    Indicates that the two entities (typically teams) are competing against each other within the same division.
  • D. isGenerationalShowdown
    Indicates a competitive or confrontational situation between members of different generations, often highlighting contrasts in age, values, or experience.
  • E. isWorldChampionshipFight
    Indicates that a given fight is officially recognized as a world championship bout for a title in its sport.
  • 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_69bd443e941881908eb4e8c685b6f656 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7517af308190bab5507a9344bf68 completed March 20, 2026, 4:25 p.m.
PD Predicate disambiguation batch_69bd7159adc881909effd4382c395c66 completed March 20, 2026, 4:10 p.m.
Created at: March 20, 2026, 1:39 p.m.