Triple
T28549431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd Eldredge |
E722839
|
entity |
| Predicate | OlympicParticipantInYear |
P25187
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Todd Eldredge, OlympicParticipantInYear, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OlympicParticipantInYear Context triple: [Todd Eldredge, OlympicParticipantInYear, 1992]
-
A.
OlympicAppearanceYear
chosen
Indicates the specific year in which an entity participated in or appeared at the Olympic Games.
-
B.
olympicMedalYear
Indicates the year in which an Olympic medal was awarded for a particular event or athlete.
-
C.
olympicYear
Indicates that the subject is associated with, occurs in, or is designated for a specific year of the Olympic Games.
-
D.
representedAtOlympics
Indicates that an entity served as an official representative (e.g., athlete, team, or delegation) for another entity at a specific edition of the Olympic Games.
-
E.
recognizedAsOlympicInYear
Indicates that an event, sport, or discipline was officially recognized as part of the Olympic Games in a specified year.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 3:41 a.m.