Triple
T16906228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Anita Park |
E424568
|
entity |
| Predicate | hasStablingCapacity |
P125159
|
FINISHED |
| Object | over 1,800 horses |
—
|
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: over 1,800 horses | Statement: [Santa Anita Park, hasStablingCapacity, over 1,800 horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStablingCapacity Context triple: [Santa Anita Park, hasStablingCapacity, over 1,800 horses]
-
A.
hasStabling
Indicates that one entity provides or contains stabling facilities (such as stalls or accommodation) for another, typically for animals like horses.
-
B.
hasPaddock
Indicates that one entity possesses or is associated with a specific paddock area or enclosure.
-
C.
hasTypeOfStalls
Indicates that an entity features or includes stalls of a particular type or category.
-
D.
hasEquestrianFacility
Indicates that a place or property includes facilities specifically designed for horse-related activities, such as riding, training, or boarding.
-
E.
hasStandingArea
Indicates that an entity includes or provides a designated area where people can stand.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3ca392ff48190ab28f0bd3e9fc376 |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:30 a.m.