Triple
T25675117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basirhat subdivision |
E643782
|
entity |
| Predicate | hasBorderIssue |
P105640
|
FINISHED |
| Object | cross-border movement and smuggling concerns |
—
|
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 movement and smuggling concerns | Statement: [Basirhat subdivision, hasBorderIssue, cross-border movement and smuggling concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderIssue Context triple: [Basirhat subdivision, hasBorderIssue, cross-border movement and smuggling concerns]
-
A.
borderIssue
chosen
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
hasBorderConflictWith
Indicates a relationship where two entities share a disputed boundary or are involved in an ongoing or historical conflict over their common border.
-
D.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
E.
hadBorder
Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 7:36 p.m.