Triple
T36988044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncle Mo |
E915016
|
entity |
| Predicate | progenyNyquistAchievement |
P131001
|
FINISHED |
| Object | 2016 Kentucky Derby winner |
—
|
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 Kentucky Derby winner | Statement: [Uncle Mo, progenyNyquistAchievement, 2016 Kentucky Derby winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progenyNyquistAchievement Context triple: [Uncle Mo, progenyNyquistAchievement, 2016 Kentucky Derby winner]
-
A.
progenyAchievement
chosen
Indicates that an individual’s offspring has attained a notable accomplishment, status, or success.
-
B.
motherAchievement
Indicates that a mother has accomplished or attained a specific achievement or notable success.
-
C.
fatherAchievement
Indicates that an achievement or accomplishment is attributed to, earned by, or associated with the father in relation to another entity.
-
D.
childProdigy
Indicates that an entity is a child who demonstrates exceptional skill or talent in a particular domain at an unusually young age.
-
E.
progenitorOf
Indicates that one entity is the direct biological or ancestral source (parent or originator) of another entity.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.