Triple
T27023496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tachileik |
E680726
|
entity |
| Predicate | crossBorderGatewayFor |
P166637
|
FINISHED |
| Object | trade |
—
|
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: trade | Statement: [Tachileik, crossBorderGatewayFor, trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderGatewayFor Context triple: [Tachileik, crossBorderGatewayFor, trade]
-
A.
crossBorderNode
Indicates a connection or element that spans or links entities across a defined boundary or border.
-
B.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
C.
crossBorderPresence
Indicates that an entity maintains operations, activities, or influence that extend across national or jurisdictional borders.
-
D.
crossBorderLinks
Indicates connections or interactions that extend across or link entities in different geographic or political jurisdictions.
-
E.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
- 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_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 27, 2026, 7:09 a.m.