Triple
T7677019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mae Sai |
E173886
|
entity |
| Predicate | hasNearbyBorderPoint |
P55118
|
FINISHED |
| Object | northernmost area of Thailand (in Mae Sai District) |
—
|
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: northernmost area of Thailand (in Mae Sai District) | Statement: [Mae Sai, hasNearbyBorderPoint, northernmost area of Thailand (in Mae Sai District)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBorderPoint Context triple: [Mae Sai, hasNearbyBorderPoint, northernmost area of Thailand (in Mae Sai District)]
-
A.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
B.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
C.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
D.
nearBorderBetween
chosen
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
E.
hasBorderLocality
Indicates that one locality is situated along or adjacent to the border of another locality.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.