Triple

T5038670
Position Surface form Disambiguated ID Type / Status
Subject Houston Astros–Texas Rangers rivalry E113490 entity
Predicate isIntraDivisionRivalry P903 FINISHED
Object true 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: true | Statement: [Houston Astros–Texas Rangers rivalry, isIntraDivisionRivalry, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isIntraDivisionRivalry
Context triple: [Houston Astros–Texas Rangers rivalry, isIntraDivisionRivalry, true]
  • A. hasLocalRivalry
    Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
  • 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. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • D. isDivisionalMatchup
    Indicates that the two entities (typically teams) are competing against each other within the same division.
  • E. hasRivalrySport
    Indicates a competitive relationship in which two entities are rivals specifically within the context of a sport or sporting activity.
  • 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_69bd44384298819089c49e7c330ec7b8 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73dbf00c819094b67809dafdecc6 completed March 20, 2026, 4:20 p.m.
PD Predicate disambiguation batch_69bd71529d608190a53470ba6c14bb1d completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:37 p.m.