Triple
T27323467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myanmar–Laos border |
E689574
|
entity |
| Predicate | crossingConnectsTownInLaos |
P168946
|
FINISHED |
| Object | Xieng Kok |
—
|
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: Xieng Kok | Statement: [Myanmar–Laos border, crossingConnectsTownInLaos, Xieng Kok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossingConnectsTownInLaos Context triple: [Myanmar–Laos border, crossingConnectsTownInLaos, Xieng Kok]
-
A.
connectedBySacbeTo
Indicates that one entity is linked or joined to another by a sacbe, an ancient raised road or causeway.
-
B.
connectedToMainlandBy
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
-
C.
connectsProvincesAlong
Indicates a relationship where something serves as a link or route joining multiple provinces along a specified path or alignment.
-
D.
connectsInlandToBorder
Indicates that an inland location is linked or provides a route to a border location.
-
E.
connectsInlandCommunitiesTo
Indicates a relationship in which something serves as a link or conduit between inland communities and another place, system, or network.
- F. None of above. chosen
Provenance (4 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_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 11:34 a.m.