Triple
T22844448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prix du Jockey Club |
E566174
|
entity |
| Predicate | typicalRunningSurfaceCondition |
P50583
|
FINISHED |
| Object | turf, varying going |
—
|
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, varying going | Statement: [Prix du Jockey Club, typicalRunningSurfaceCondition, turf, varying going]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRunningSurfaceCondition Context triple: [Prix du Jockey Club, typicalRunningSurfaceCondition, turf, varying going]
-
A.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
B.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
C.
typicalTrailConditions
Indicates the usual or expected state of a trail’s surface and environment under normal conditions.
-
D.
runningTerrain
Indicates the type of ground or surface on which the running activity takes place.
-
E.
hasCourtSurface
Indicates that something (such as a court or playing area) possesses a specific type of surface.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8726d4819095b4d999b4172ff7 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:36 p.m.