Triple
T18068167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntly |
E432346
|
entity |
| Predicate | distanceToHamiltonApproxKm |
P95530
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Huntly, distanceToHamiltonApproxKm, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHamiltonApproxKm Context triple: [Huntly, distanceToHamiltonApproxKm, 30]
-
A.
distanceFromHamilton
chosen
Indicates the spatial distance between a given entity and the location identified as Hamilton.
-
B.
approximateDistanceKm
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
C.
approximateRouteLength
Indicates the estimated total distance or length of a given route, rather than its exact measured value.
-
D.
tourDistanceApproxKm
Indicates an approximate total distance, measured in kilometers, covered during a tour or journey.
-
E.
depthApproxKm
Indicates the approximate depth of something measured in kilometers.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cceb020081909329492591e7b1f2 |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.