Triple

T6722733
Position Surface form Disambiguated ID Type / Status
Subject Ibrox Stadium E153434 entity
Predicate hasRivalryContext P72886 FINISHED
Object Old Firm matches 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: Old Firm matches | Statement: [Ibrox Stadium, hasRivalryContext, Old Firm matches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRivalryContext
Context triple: [Ibrox Stadium, hasRivalryContext, Old Firm matches]
  • A. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • B. hasSubRivalryContext
    Indicates that one rivalry context is a more specific, subordinate part of a broader rivalry context within the same overall competitive relationship.
  • C. hasLocalRivalry
    Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
  • D. hasRivalryEmotion
    Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
  • E. hasHistoricRivalry
    Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
  • 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_69c6880afb988190ad88011b48ecfcba completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d139d50c81908b19120f139deaa5 completed March 27, 2026, 6:49 p.m.
PD Predicate disambiguation batch_69c6d08c5d348190a29dee668c398e70 completed March 27, 2026, 6:46 p.m.
PDg Predicate description generation batch_69c6d11fab808190b18160ff3829fcc6 completed March 27, 2026, 6:49 p.m.
Created at: March 27, 2026, 2:08 p.m.