Triple
T17662566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Breeders' Cup Classic |
E440287
|
entity |
| Predicate | raceNumberInCard |
P59494
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [2016 Breeders' Cup Classic, raceNumberInCard, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceNumberInCard Context triple: [2016 Breeders' Cup Classic, raceNumberInCard, 12]
-
A.
racingNumber
chosen
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
-
B.
raceNumberInSeason
Indicates the ordinal position of a specific race within the sequence of races in a given season.
-
C.
raceName
Indicates the specific race or competition designation associated with an entity or event.
-
D.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
E.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
- 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:51 a.m.