Triple
T20534299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Derby |
E504152
|
entity |
| Predicate | approximateDistanceInMetres |
P25800
|
FINISHED |
| Object | 2000 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: 2000 metres | Statement: [Canadian Derby, approximateDistanceInMetres, 2000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceInMetres Context triple: [Canadian Derby, approximateDistanceInMetres, 2000 metres]
-
A.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
B.
approximateLengthInMeters
chosen
Indicates the estimated or roughly measured length of something expressed in meters.
-
C.
approximateDistanceUnit
Indicates that the distance value is expressed in an approximate or non-exact unit of measurement.
-
D.
approximateDistanceKm
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
E.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06df04081908fa95c6214f06093 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.