Triple
T27023363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myawaddy border checkpoint |
E680722
|
entity |
| Predicate | borderDirectionFromMyanmar |
P186346
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [Myawaddy border checkpoint, borderDirectionFromMyanmar, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionFromMyanmar Context triple: [Myawaddy border checkpoint, borderDirectionFromMyanmar, east]
-
A.
borderTypeWithMyanmar
Indicates the specific nature or classification of the border relationship that an entity has with Myanmar.
-
B.
borderDirectionFromSingapore
Indicates the directional orientation of another location’s border relative to Singapore.
-
C.
hasBorderTownOnMyanmarSide
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
D.
borderDirectionFromCapital
Indicates the compass direction from a country's capital city to a specified border or neighboring entity.
-
E.
borderDirectionFromUS
Indicates the compass direction in which a country or region lies relative to the United States along their shared border.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 27, 2026, 7:09 a.m.