Triple
T35372969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Turkey border |
E1021824
|
entity |
| Predicate | borderSecurityIssue |
P16224
|
FINISHED |
| Object | smuggling |
—
|
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: smuggling | Statement: [Iran–Turkey border, borderSecurityIssue, smuggling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSecurityIssue Context triple: [Iran–Turkey border, borderSecurityIssue, smuggling]
-
A.
borderIssue
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
-
B.
borderConcern
chosen
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
C.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
-
D.
borderPass
Indicates that one entity crosses or moves through the boundary separating two regions or jurisdictions.
-
E.
borderGuardDuty
Indicates that an entity is assigned to perform security or monitoring duties at a border or checkpoint.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 3, 2026, 4:03 p.m.