Triple
T21901200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wood Memorial Stakes |
E540811
|
entity |
| Predicate | hasDistanceUnit |
P145577
|
FINISHED |
| Object | miles |
—
|
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: miles | Statement: [Wood Memorial Stakes, hasDistanceUnit, miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceUnit Context triple: [Wood Memorial Stakes, hasDistanceUnit, miles]
-
A.
approximateDistanceUnit
Indicates that the distance value is expressed in an approximate or non-exact unit of measurement.
-
B.
distanceMeasurementMethod
Indicates the method or technique used to determine or measure the distance between entities.
-
C.
hasDistanceReference
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
-
D.
hasDistanceCategory
Indicates that one entity is associated with a qualitative or categorical classification of its distance relative to another entity or reference point.
-
E.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fcb18748190a21071c122b7e6d5 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 7:16 p.m.