Triple
T16354239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Intelligence North |
E397132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional intelligence formation |
C37330
|
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: regional intelligence formation Context triple: [Joint Intelligence North, instanceOf, regional intelligence formation]
-
A.
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.
-
B.
regional organisation
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
C.
regional institute
A regional institute is an organization dedicated to education, research, or specialized services that primarily serves and addresses the needs of a specific geographic area or region.
-
D.
regional forum
A regional forum is a structured platform where stakeholders from a specific geographic area gather to discuss, coordinate, and address shared issues, policies, and development priorities.
-
E.
geospatial intelligence facility
A geospatial intelligence facility is a secure, specialized site where experts collect, process, analyze, and disseminate geographic and imagery data to support military, intelligence, and strategic decision-making.
- F. None of above. chosen
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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.