Triple

T35959655
Position Surface form Disambiguated ID Type / Status
Subject Summit E1039959 entity
Predicate firstRankedAsWorldsFastest P103692 FINISHED
Object June 2018 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: June 2018 | Statement: [Summit, firstRankedAsWorldsFastest, June 2018]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: firstRankedAsWorldsFastest
Context triple: [Summit, firstRankedAsWorldsFastest, June 2018]
  • A. wasWorldRecordFor
    Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
  • B. maximumSpeedRecord
    Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
  • C. heldWorldRecordTime
    Indicates that an entity achieved and maintained the fastest known performance time in a specific event or activity, recognized as the official world record for a period.
  • D. worldRecordTime
    Indicates that an entity’s recorded time for an event is the fastest ever achieved globally, i.e., the official world record time for that event.
  • E. firstTimeWorldNumberOne chosen
    Indicates that the entity reached the world number one ranking for the first time.
  • 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_69f76e26b21081909fd9ffb3aff6c77a completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a0895b48190acdd88dc10db7be7 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:07 p.m.