Triple
T32503232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko Sichang |
E830717
|
entity |
| Predicate | distanceFromBangkokApprox |
P29501
|
FINISHED |
| Object | about 100 km southeast |
—
|
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 100 km southeast | Statement: [Ko Sichang, distanceFromBangkokApprox, about 100 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBangkokApprox Context triple: [Ko Sichang, distanceFromBangkokApprox, about 100 km southeast]
-
A.
distanceFromBangkok
chosen
Indicates the spatial distance between a given location and the city of Bangkok.
-
B.
distanceFromThonBuriStation_km
Indicates the distance, measured in kilometers, between a given entity and Thon Buri Station.
-
C.
approximateDistanceInKilometersFromChiangMai
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and Chiang Mai.
-
D.
distanceFromPhuket
Indicates the measured distance between a given entity or location and Phuket.
-
E.
distanceFromPattaya
Indicates the spatial distance between a given place or object and the location of Pattaya.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:59 a.m.