Triple
T29175774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 500 m speed skating at the 2006 Winter Olympics |
E739602
|
entity |
| Predicate | isSprintEvent |
P166388
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [500 m speed skating at the 2006 Winter Olympics, isSprintEvent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSprintEvent Context triple: [500 m speed skating at the 2006 Winter Olympics, isSprintEvent, true]
-
A.
isSprintRelay
Indicates that the event is a relay race run over a short sprint distance, with team members completing sequential legs.
-
B.
isSprintChampionshipRace
Indicates that the race is designated as the sprint championship event within a competition or season.
-
C.
isSprint
Indicates that an entity represents a short, time-boxed iteration or development cycle within a larger project or process.
-
D.
isRelayRace
Indicates that the activity or event is a relay race, where multiple participants or teams take turns completing segments of a race in sequence.
-
E.
sprintRace
Indicates a competitive running event over a short distance where participants race to finish in the fastest time.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663403c048190ae61c2a304e59d5a |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:54 a.m.