Triple
T26493583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tak province |
E669221
|
entity |
| Predicate | hasMajorBorderTown |
P15361
|
FINISHED |
| Object | Mae Sot |
—
|
NE NERFINISHED |
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: Mae Sot | Statement: [Tak province, hasMajorBorderTown, Mae Sot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorBorderTown Context triple: [Tak province, hasMajorBorderTown, Mae Sot]
-
A.
hasBorderCity
chosen
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
B.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
C.
hasNotableBuildingOnBorder
Indicates that a notable or significant building is located directly on or straddling the border between two areas or entities.
-
D.
isBorderTownBetween
Indicates that a town is located on or near the boundary separating two specified regions, serving as a border settlement between them.
-
E.
hasBorderTownOnCanadianSide
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 27, 2026, 1:06 a.m.