Triple
T16686524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sword Dancer Stakes |
E405475
|
entity |
| Predicate | usualTrackCondition |
P56761
|
FINISHED |
| Object | turf |
—
|
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: turf | Statement: [Sword Dancer Stakes, usualTrackCondition, turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualTrackCondition Context triple: [Sword Dancer Stakes, usualTrackCondition, turf]
-
A.
usedCondition
Indicates that one entity is employed or applied under a particular state, requirement, or circumstance defined by another entity.
-
B.
typicalCircumstance
chosen
Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
-
C.
standardTrackStatus
Indicates the current state or phase of a track within a standardized processing, review, or lifecycle workflow.
-
D.
globalCondition
Indicates that a condition applies universally or system-wide rather than being limited to a specific local context or subset.
-
E.
navigationCondition
Indicates the specific circumstances or requirements that must be satisfied for a navigation action or route to be valid or taken.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea63b7081908a055036172f9683 |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.