Triple
T17662367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unbridled's Song |
E440283
|
entity |
| Predicate | finishedPositionInKentuckyDerby |
P55492
|
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: [Unbridled's Song, finishedPositionInKentuckyDerby, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishedPositionInKentuckyDerby Context triple: [Unbridled's Song, finishedPositionInKentuckyDerby, 5]
-
A.
usualDayRelationToKentuckyDerby
Indicates the temporal relationship between a given day and the day on which the Kentucky Derby is typically held.
-
B.
finishPosition
chosen
Indicates the final rank or place an entity achieves in an ordered outcome, such as a race, competition, or sequence of results.
-
C.
permanentReturnToPimlico
Indicates a lasting relocation or re-establishment to Pimlico, implying the subject returns there to stay indefinitely rather than temporarily.
-
D.
positionOnRace
Indicates the relative ranking or placement an entity holds within the context of a race or competitive event.
-
E.
bestRaceFinishPositionAchievedByDriver
Indicates the best (highest-ranking) race finishing position that a particular driver has ever achieved.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea73c90819087a23a7b6171f581 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:48 a.m.