Triple
T24256620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5000 metres at the 2016 Summer Olympics |
E603687
|
entity |
| Predicate | finalHeldOn |
P112958
|
FINISHED |
| Object | 2016-08-20 |
—
|
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: 2016-08-20 | Statement: [5000 metres at the 2016 Summer Olympics, finalHeldOn, 2016-08-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalHeldOn Context triple: [5000 metres at the 2016 Summer Olympics, finalHeldOn, 2016-08-20]
-
A.
finalHeld
Indicates that an entity ultimately retains possession or control of another entity at the conclusion of a process or event.
-
B.
finalUsuallyHeldIn
Indicates that the final stage or concluding event of something is typically conducted or takes place in a particular location or venue.
-
C.
finalDay
chosen
Indicates that a given day is the last or concluding day within a specified period, event, or sequence.
-
D.
finalGrandPrix
Indicates that a given Grand Prix event is the last one in a specified sequence, season, or career.
-
E.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6395108190b5310f76e7d78c41 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.