Triple

T26230003
Position Surface form Disambiguated ID Type / Status
Subject Los Leones E656007 entity
Predicate associatedWithMainRivalryType P146762 FINISHED
Object regional rivalry 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: regional rivalry | Statement: [Los Leones, associatedWithMainRivalryType, regional rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithMainRivalryType
Context triple: [Los Leones, associatedWithMainRivalryType, regional rivalry]
  • A. associatedRivalry
    Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
  • B. hasRivalryRoot
    Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
  • C. isPartOfRivalry
    Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
  • D. hasRivalryCategory chosen
    Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
  • E. isMajorRivalryFor
    Indicates that one entity is a primary or highly significant competitor or adversary to another, often characterized by ongoing, notable, or intense rivalry.
  • 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_69ee5b4b8b408190993da38c0067cc8d completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69fef112398081909237c3872345968b completed May 9, 2026, 8:32 a.m.
PD Predicate disambiguation batch_69feefb14ec08190ab401987d8c84a23 completed May 9, 2026, 8:26 a.m.
Created at: April 26, 2026, 8:59 p.m.