Triple

T24792031
Position Surface form Disambiguated ID Type / Status
Subject Michelin Endurance Cup E620274 entity
Predicate timingOfPoints P157307 FINISHED
Object race finish 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: race finish | Statement: [Michelin Endurance Cup, timingOfPoints, race finish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timingOfPoints
Context triple: [Michelin Endurance Cup, timingOfPoints, race finish]
  • A. timeCoordinate
    Indicates a relationship where a specific time value is used to locate or reference an event, state, or object along a temporal axis or timeline.
  • B. timeCoordinateType
    Indicates the specific temporal reference system or framework used to define and interpret time coordinates for an event or entity.
  • C. timingOfRace
    Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
  • D. timeIndexed
    Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
  • E. timingParameter
    Indicates a relationship where one entity specifies or controls a temporal setting, constraint, or configuration parameter that determines the timing behavior of another entity or process.
  • 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_69e2fabe77c8819085f7ce6486248139 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f42b11251881908070b93355de64ad completed May 1, 2026, 4:24 a.m.
Created at: April 18, 2026, 4:47 a.m.