Triple

T18318438
Position Surface form Disambiguated ID Type / Status
Subject Fantastic Light E438806 entity
Predicate notableRaceRivalry P102218 FINISHED
Object 2001 Irish Champion Stakes vs Galileo 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: 2001 Irish Champion Stakes vs Galileo | Statement: [Fantastic Light, notableRaceRivalry, 2001 Irish Champion Stakes vs Galileo]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableRaceRivalry
Context triple: [Fantastic Light, notableRaceRivalry, 2001 Irish Champion Stakes vs Galileo]
  • A. notableRivalry
    Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
  • B. rivalryBasis
    Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
  • C. associatedRivalry
    Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
  • D. notableRivalryElement chosen
    Indicates that one entity is a significant component, example, or instance within a notable rivalry between two or more entities.
  • 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_69d8b916a2d081909e249e4902f6aad9 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50aa342a881909afcd995405027af completed April 19, 2026, 5:02 p.m.
PD Predicate disambiguation batch_69e44fe4ee10819086b4142444fca1f5 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:36 a.m.