Triple
T15261023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kauto Star |
E364773
|
entity |
| Predicate | numberOfWinsInKingGeorgeVIChase |
P117816
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Kauto Star, numberOfWinsInKingGeorgeVIChase, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfWinsInKingGeorgeVIChase Context triple: [Kauto Star, numberOfWinsInKingGeorgeVIChase, 5]
-
A.
championJockeyTitleEndYear
Indicates the year in which a jockey’s tenure as champion jockey came to an end.
-
B.
BritishChampionIn
Indicates that an entity holds or has held the status of British champion in a specified field, event, or competition at a given time or place.
-
C.
EpsomDerbyWinningTrainer
Indicates that the subject is the trainer who trained the winning horse of the Epsom Derby in the specified year or event.
-
D.
tripleCrownWinner
Indicates that an entity has won all three major titles or championships that together constitute a "Triple Crown" within a particular sport or competitive domain.
-
E.
wonPremiershipIn
Indicates that an entity secured victory in a premiership competition in a specified year or season.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084e85a08190b8e63598b9f6a535 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.