Triple
T34293308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prentice Alvin "Pat" Day |
E879951
|
entity |
| Predicate | trackAssociation |
P118645
|
FINISHED |
| Object | Churchill Downs |
—
|
NE NERFINISHED |
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: Churchill Downs | Statement: [Prentice Alvin "Pat" Day, trackAssociation, Churchill Downs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackAssociation Context triple: [Prentice Alvin "Pat" Day, trackAssociation, Churchill Downs]
-
A.
trailAssociation
Indicates an associative relationship between entities where one is contextually or functionally linked to a trail (such as being located on, connected to, or part of that trail).
-
B.
associatedWithTrack
chosen
Indicates a relationship in which an entity is linked or connected to a specific track, such as being part of, derived from, or relevant to that track.
-
C.
sceneAssociation
Indicates a contextual or thematic relationship linking entities that co-occur or interact within the same scene.
-
D.
trackFrom
Indicates a source or origin from which something is tracked or monitored.
-
E.
trackRole
Indicates that an entity holds or performs a specific role within the context of a particular track or sequence of 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:57 a.m.