Triple
T17839671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King's Stand Stakes |
E445488
|
entity |
| Predicate | typicalSurfaceCondition |
P1242
|
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: [King's Stand Stakes, typicalSurfaceCondition, turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSurfaceCondition Context triple: [King's Stand Stakes, typicalSurfaceCondition, turf]
-
A.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
B.
typicalTexture
Indicates the usual or characteristic surface feel or consistency that is commonly associated with an entity.
-
C.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
-
D.
potentialSurfaceConditions
Indicates the possible environmental or physical conditions that could exist on a surface under given circumstances or assumptions.
-
E.
surfaceConditionCertainty
Indicates the degree of confidence or certainty about the described condition of a 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d2a570c81909787296bde7e795c |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.