Triple
T22450594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Orleans Classic Stakes |
E554977
|
entity |
| Predicate | approximateMetricDistance |
P25800
|
FINISHED |
| Object | 1800 metres |
—
|
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: 1800 metres | Statement: [New Orleans Classic Stakes, approximateMetricDistance, 1800 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateMetricDistance Context triple: [New Orleans Classic Stakes, approximateMetricDistance, 1800 metres]
-
A.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
B.
distanceMetric
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
C.
approximateDistanceUnit
Indicates that the distance value is expressed in an approximate or non-exact unit of measurement.
-
D.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
-
E.
approximateLengthInMeters
chosen
Indicates the estimated or roughly measured length of something expressed in meters.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4ba6a88190a0a79e2c20fa8c08 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.