Triple
T19151982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's individual sprint at the 2008 Summer Olympics |
E468830
|
entity |
| Predicate | distancePerRace |
P134622
|
FINISHED |
| Object | 3 laps |
—
|
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: 3 laps | Statement: [men's individual sprint at the 2008 Summer Olympics, distancePerRace, 3 laps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distancePerRace Context triple: [men's individual sprint at the 2008 Summer Olympics, distancePerRace, 3 laps]
-
A.
raceDistanceType
Indicates the specific type or category of distance over which a race is conducted.
-
B.
raceDistanceApprox
Indicates that the distance of a race is approximately equal to a specified value, allowing for some margin of error rather than requiring an exact match.
-
C.
majorRaceDistance
Indicates the standard or primary distance over which a major race or competition is contested.
-
D.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
E.
trackRecordDistance
Indicates that one entity holds the record for the greatest distance achieved in a particular tracking or performance context.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97dc5a481909a58416126a0862d |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.