Triple

T24578855
Position Surface form Disambiguated ID Type / Status
Subject 4 × 400 metres relay E608189 entity
Predicate typicalOrderOfRunners P156411 FINISHED
Object strong starter on first leg 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: strong starter on first leg | Statement: [4 × 400 metres relay, typicalOrderOfRunners, strong starter on first leg]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOrderOfRunners
Context triple: [4 × 400 metres relay, typicalOrderOfRunners, strong starter on first leg]
  • A. baseRunners
    Indicates that certain players are currently occupying one or more bases as runners in a baseball play or game situation.
  • B. frontRunnerAtStart
    Indicates that an entity is the leading competitor or in first position at the beginning of an event or process.
  • C. eventualFrontRunner
    Indicates that an entity is expected or predicted to become the leading or most successful one among a set of competitors in the future.
  • D. runnerType
    Indicates the specific category or style of running associated with an entity (e.g., sprinter, marathoner, trail runner).
  • E. firstRunningWinner
    Indicates that the subject is the first entity to win among those participating in a running event or race.
  • 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_69e2c4cdab6c8190aae6e5d3de55c95e completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a97cd0d4819091bf0841fa8e108a completed April 30, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f2a6c1f07081908edf0b521767e79b completed April 30, 2026, 12:48 a.m.
PDg Predicate description generation batch_69f2a846c5bc81909ba50cee483bea91 completed April 30, 2026, 12:54 a.m.
Created at: April 18, 2026, 2:29 a.m.