Triple
T30009567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zokhawthar–Rikhawdar crossing |
E762419
|
entity |
| Predicate | borderSideSettlementInMyanmar |
P85286
|
FINISHED |
| Object | Rikhawdar |
—
|
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: Rikhawdar | Statement: [Zokhawthar–Rikhawdar crossing, borderSideSettlementInMyanmar, Rikhawdar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSideSettlementInMyanmar Context triple: [Zokhawthar–Rikhawdar crossing, borderSideSettlementInMyanmar, Rikhawdar]
-
A.
borderTypeWithMyanmar
Indicates the specific nature or classification of the border relationship that an entity has with Myanmar.
-
B.
hasBorderTownOnMyanmarSide
chosen
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
C.
borderDirectionFromMyanmar
Indicates the compass direction in which another country or region lies along its shared border with Myanmar.
-
D.
hasBorderStatesOnMyanmarSide
Indicates that the referenced entity consists of or includes the states that share a land border with Myanmar.
-
E.
hasInternationalBoundaryLengthWithMyanmar
Indicates the measured length of the international land or maritime boundary shared between a given entity and Myanmar.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 29, 2026, 6:43 p.m.