Triple
T10172717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonamura |
E235369
|
entity |
| Predicate | hasBorderRelatedActivity |
P80566
|
FINISHED |
| Object | cross-border commerce with Bangladesh |
—
|
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: cross-border commerce with Bangladesh | Statement: [Sonamura, hasBorderRelatedActivity, cross-border commerce with Bangladesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderRelatedActivity Context triple: [Sonamura, hasBorderRelatedActivity, cross-border commerce with Bangladesh]
-
A.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
B.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
C.
hasCrossBorderInteraction
chosen
Indicates that there is an interaction, activity, or relationship occurring between entities located in different countries or jurisdictions.
-
D.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
E.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9f6dd8819081588600499165ee |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.