Triple
T7866658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doi Suthep |
E182632
|
entity |
| Predicate | approxDistanceFromCityCenter |
P1299
|
FINISHED |
| Object | about 15 kilometers from central Chiang Mai |
—
|
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: about 15 kilometers from central Chiang Mai | Statement: [Doi Suthep, approxDistanceFromCityCenter, about 15 kilometers from central Chiang Mai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxDistanceFromCityCenter Context triple: [Doi Suthep, approxDistanceFromCityCenter, about 15 kilometers from central Chiang Mai]
-
A.
nearestCityCenterDistance
Indicates the distance from a given location to the closest city center.
-
B.
distanceFromDowntown
chosen
Indicates the physical distance between a given location and the central downtown area.
-
C.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
D.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
E.
distanceFromMajorCity
Indicates the measured distance between a given location and a specified major city.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb38464274819080f182b53783fa84 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:54 p.m.