Triple

T28704305
Position Surface form Disambiguated ID Type / Status
Subject Inver Park E729643 entity
Predicate hasLocalRivalryMatch P18267 FINISHED
Object Larne F.C. vs Carrick Rangers F.C. 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: Larne F.C. vs Carrick Rangers F.C. | Statement: [Inver Park, hasLocalRivalryMatch, Larne F.C. vs Carrick Rangers F.C.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalRivalryMatch
Context triple: [Inver Park, hasLocalRivalryMatch, Larne F.C. vs Carrick Rangers F.C.]
  • A. hasLocalRivalry chosen
    Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
  • B. hasLocalRivalryVenueWith
    Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
  • C. hasRivalryContext
    Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
  • D. hasHomeStadiumInRivalry
    Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
  • E. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • 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_69f043e6e9688190b6bdd6e5665498ff completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f7be53890081909b1d93f30a8f31c6 completed May 3, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69f7bccacbac8190978976324c67db28 completed May 3, 2026, 9:23 p.m.
Created at: April 28, 2026, 5:44 a.m.