Triple
T14482785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lance Armstrong |
E359151
|
entity |
| Predicate | dopingAdmissionYear |
P114373
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Lance Armstrong, dopingAdmissionYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dopingAdmissionYear Context triple: [Lance Armstrong, dopingAdmissionYear, 2013]
-
A.
notableDopingCase
Indicates that an entity is recognized for being involved in a significant or widely known doping (use of banned performance-enhancing substances) incident or scandal.
-
B.
youthOlympicDebutYear
Indicates the year in which an entity first participated in or was introduced to the Youth Olympic Games.
-
C.
recognizedAsOlympicInYear
Indicates that an event, sport, or discipline was officially recognized as part of the Olympic Games in a specified year.
-
D.
olympicDebut
Indicates the event or year in which an entity first participated in the Olympic Games.
-
E.
antiDopingControl
Indicates that an entity conducts, undergoes, or is associated with procedures to detect and prevent the use of prohibited performance-enhancing substances or methods.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924bc548819087a2f693840d7426 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.