Triple
T27323464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myanmar–Laos border |
E689574
|
entity |
| Predicate | southernTerminusCountry |
P162542
|
FINISHED |
| Object | Laos |
—
|
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: Laos | Statement: [Myanmar–Laos border, southernTerminusCountry, Laos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southernTerminusCountry Context triple: [Myanmar–Laos border, southernTerminusCountry, Laos]
-
A.
southernTerminusCountry
chosen
Indicates the country in which the southern endpoint or terminus of something (such as a route, line, or feature) is located.
-
B.
easternTerminusCountry
Indicates the country in which the eastern terminus (end point) of something, such as a route or infrastructure, is located.
-
C.
terminusA_country
Indicates the country in which the starting terminus (terminus A) of a route, line, or connection is located.
-
D.
westernTerminusCountry
Indicates the country in which the westernmost endpoint of something (such as a route, line, or feature) is located.
-
E.
terminusB_country
Indicates that the country specified is the location of the endpoint (terminus B) of a route, connection, or infrastructure segment.
- 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_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 11:34 a.m.