Triple
T27323466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myanmar–Laos border |
E689574
|
entity |
| Predicate | crossingConnectsTownInMyanmar |
P85286
|
FINISHED |
| Object | Kenglap |
—
|
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: Kenglap | Statement: [Myanmar–Laos border, crossingConnectsTownInMyanmar, Kenglap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossingConnectsTownInMyanmar Context triple: [Myanmar–Laos border, crossingConnectsTownInMyanmar, Kenglap]
-
A.
hasBorderTownOnMyanmarSide
chosen
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
B.
distanceFromMawlamyine_km
Indicates the distance, measured in kilometers, between a given place or entity and Mawlamyine.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
connectsInlandToBorder
Indicates that an inland location is linked or provides a route to a border location.
-
E.
connectedToMainlandBy
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 11:34 a.m.