Triple
T27276103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratchaburi |
E688196
|
entity |
| Predicate | approximateDistanceInKilometersFromBangkok |
P29501
|
FINISHED |
| Object | about 80 |
—
|
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 80 | Statement: [Ratchaburi, approximateDistanceInKilometersFromBangkok, about 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceInKilometersFromBangkok Context triple: [Ratchaburi, approximateDistanceInKilometersFromBangkok, about 80]
-
A.
distanceFromBangkok
chosen
Indicates the spatial distance between a given location and the city of Bangkok.
-
B.
approximateDistanceInKilometersFromChiangMai
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and Chiang Mai.
-
C.
distanceFromThonBuriStation_km
Indicates the distance, measured in kilometers, between a given entity and Thon Buri Station.
-
D.
approximateDistanceInKilometresFromLuangPrabang
Indicates the estimated distance, measured in kilometres, between an entity and the location of Luang Prabang.
-
E.
distanceFromPhuket
Indicates the measured distance between a given entity or location and Phuket.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 11:02 a.m.