Triple
T36946638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyson Gay |
E913929
|
entity |
| Predicate | timeIn200MetresRank |
P187227
|
FINISHED |
| Object | one of the fastest times in history |
—
|
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: one of the fastest times in history | Statement: [Tyson Gay, timeIn200MetresRank, one of the fastest times in history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeIn200MetresRank Context triple: [Tyson Gay, timeIn200MetresRank, one of the fastest times in history]
-
A.
timeIn100MetresEqualled
Indicates that two entities recorded exactly the same time in a 100-metre event.
-
B.
personalBestTimeIn100Metres
Indicates the best (fastest) time an individual has ever achieved in a 100-metre race.
-
C.
goldMedalWinnerIn men's 100 metres
Indicates that the subject is the athlete who won the gold medal in the men's 100 metres event in a specified competition.
-
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.
legRunner
Indicates that an entity functions as a runner or moving component that operates in conjunction with a leg or leg-like structure.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:13 p.m.