Triple

T35816627
Position Surface form Disambiguated ID Type / Status
Subject Jan Železný E1035378 entity
Predicate worldRecordMark P197645 FINISHED
Object 98.48 m 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: 98.48 m | Statement: [Jan Železný, worldRecordMark, 98.48 m]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: worldRecordMark
Context triple: [Jan Železný, worldRecordMark, 98.48 m]
  • A. 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.
  • B. worldRecordSet
    Indicates that an entity has achieved and established the best performance ever recorded in the world for a particular activity, event, or measurable criterion.
  • C. worldRecordEvent
    Indicates that an event involves the setting, holding, or recognition of a world record.
  • D. 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.
  • E. 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.
  • 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_69f76e1762408190b885a8456862e372 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fe9fb9735c8190a360b556c9d00b3f completed May 9, 2026, 2:45 a.m.
PD Predicate disambiguation batch_69fe9eaa88008190a9b2a469dc685002 completed May 9, 2026, 2:40 a.m.
PDg Predicate description generation batch_69fe9fb88db08190a8f4af350633330e completed May 9, 2026, 2:45 a.m.
Created at: May 3, 2026, 4:06 p.m.