Triple
T4642770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churchill Downs |
E101692
|
entity |
| Predicate | mainTrackDistance |
P57550
|
FINISHED |
| Object | 1.0 mile |
—
|
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: 1.0 mile | Statement: [Churchill Downs, mainTrackDistance, 1.0 mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTrackDistance Context triple: [Churchill Downs, mainTrackDistance, 1.0 mile]
-
A.
trackRecordDistance
Indicates that one entity holds the record for the greatest distance achieved in a particular tracking or performance context.
-
B.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
C.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
D.
hasCyclingDistance
Indicates that there is a specified distance associated with traveling between entities by cycling.
-
E.
hourRecordDistance
Indicates that one entity holds or represents the record for the greatest distance covered within a one-hour time period relative to another entity or context.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a93047c8190990c94fd5a57c867 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:14 p.m.