Triple
T26199529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Myanmar |
E655192
|
entity |
| Predicate | hasBorderTradePoint |
P80015
|
FINISHED |
| Object | Muse–Ruili border crossing |
—
|
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: Muse–Ruili border crossing | Statement: [Northern Myanmar, hasBorderTradePoint, Muse–Ruili border crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderTradePoint Context triple: [Northern Myanmar, hasBorderTradePoint, Muse–Ruili border crossing]
-
A.
borderTradePointWith
chosen
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
B.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
C.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
-
D.
hasBorderTripoint
Indicates that three distinct borders or regions meet at a single common point.
-
E.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 8:47 p.m.