Triple
T21842565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran exfiltration operation |
E539290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint Canada–United States operation |
C27152
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: joint Canada–United States operation Context triple: [Tehran exfiltration operation, instanceOf, joint Canada–United States operation]
-
A.
cross‑border operation
chosen
A cross-border operation is an organized activity or transaction conducted across the legal, regulatory, or geographic boundaries of two or more countries.
-
B.
Canadian NORAD Region
The Canadian NORAD Region is the division of the North American Aerospace Defense Command responsible for aerospace warning, control, and defense operations over Canadian territory and adjacent airspace.
-
C.
regional joint task force
A regional joint task force is a collaborative, multi-agency or multi-national organization formed within a specific geographic area to coordinate and execute integrated operations toward shared security, emergency response, or policy objectives.
-
D.
Canada–Canada internal border
A Canada–Canada internal border is an administrative boundary separating provinces or territories within Canada, delineating their respective jurisdictions while remaining entirely within the sovereign territory of Canada.
-
E.
multinational military coalition
A multinational military coalition is a temporary or long-term alliance of armed forces from multiple sovereign states that coordinate resources, strategy, and operations to achieve shared security or defense objectives.
- F. None of above.
Provenance (1 batch)
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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:55 p.m.