Triple
T7066284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Brussels |
E164360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western European security pact |
C89
|
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: Western European security pact Context triple: [Treaty of Brussels, instanceOf, Western European security pact]
-
A.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
-
B.
European political alliance
A European political alliance is a cooperative grouping of political parties or states within Europe that coordinate policies, strategies, and actions to advance shared ideological or strategic interests across national borders.
-
C.
collective defense agreement
chosen
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
Economic alliance
An economic alliance is a formal or informal partnership between countries or regions designed to promote mutual economic benefits through cooperation in trade, investment, and financial policies.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:39 p.m.