Triple
T28549436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd Eldredge |
E722839
|
entity |
| Predicate | bestOlympicResultEvent |
P33011
|
FINISHED |
| Object | men's singles |
—
|
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: men's singles | Statement: [Todd Eldredge, bestOlympicResultEvent, men's singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestOlympicResultEvent Context triple: [Todd Eldredge, bestOlympicResultEvent, men's singles]
-
A.
olympicBestResult
chosen
Indicates the best performance or highest achievement an entity has attained in Olympic competition.
-
B.
bestOlympicGamesResultYear
Indicates the year in which an entity achieved its best result at the Olympic Games.
-
C.
worldRecordEvent
Indicates that an event involves the setting, holding, or recognition of a world record.
-
D.
OlympicRecordBeforeEvent
Indicates that a performance was the standing Olympic record prior to the start of a specified event.
-
E.
olympicRecordStatus
Indicates the relationship between a performance and the Olympic record, specifying whether and how that performance sets, equals, or affects the standing Olympic record.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:41 a.m.