Triple
T23698755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otis Davis |
E585526
|
entity |
| Predicate | setWorldRecordAtCompetition |
P114515
|
FINISHED |
| Object | 1960 Summer Olympics in Rome |
—
|
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: 1960 Summer Olympics in Rome | Statement: [Otis Davis, setWorldRecordAtCompetition, 1960 Summer Olympics in Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWorldRecordAtCompetition Context triple: [Otis Davis, setWorldRecordAtCompetition, 1960 Summer Olympics in Rome]
-
A.
setWorldRecordCompetition
chosen
Indicates that an entity achieved a world record performance within the context of a specific competition.
-
B.
setWorldRecordsIn
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
-
C.
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.
-
D.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
E.
setWorldRecordLocation
Indicates the place where a world record was set or achieved.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b6804970819083d4e63caa93ae4e |
completed | April 29, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.