Triple
T27023349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myawaddy border checkpoint |
E680722
|
entity |
| Predicate | oppositeSideBorderControlBy |
P35156
|
FINISHED |
| Object | Thai Immigration Bureau |
—
|
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: Thai Immigration Bureau | Statement: [Myawaddy border checkpoint, oppositeSideBorderControlBy, Thai Immigration Bureau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeSideBorderControlBy Context triple: [Myawaddy border checkpoint, oppositeSideBorderControlBy, Thai Immigration Bureau]
-
A.
borderControlSide
chosen
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
B.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
C.
hasBorderControlBy
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
D.
borderingCountryOnOtherSide
Indicates that one country lies on the opposite side of a shared border relative to another country.
-
E.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 7:09 a.m.