Triple
T29648474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Myanmar–China tripoint |
E756069
|
entity |
| Predicate | borderRegionOfMyanmar |
P12818
|
FINISHED |
| Object | Kachin State |
—
|
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: Kachin State | Statement: [India–Myanmar–China tripoint, borderRegionOfMyanmar, Kachin State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegionOfMyanmar Context triple: [India–Myanmar–China tripoint, borderRegionOfMyanmar, Kachin State]
-
A.
hasBorderStatesOnMyanmarSide
Indicates that the referenced entity consists of or includes the states that share a land border with Myanmar.
-
B.
borderTypeWithMyanmar
Indicates the specific nature or classification of the border relationship that an entity has with Myanmar.
-
C.
hasBorderTownOnMyanmarSide
Indicates that a town is located on the Myanmar side of a border shared with another country.
-
D.
borderDirectionFromMyanmar
Indicates the compass direction in which another country or region lies along its shared border with Myanmar.
-
E.
borderRegion
chosen
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 28, 2026, 6:51 p.m.