Triple
T15518163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | governments of the United States, United Kingdom, Netherlands, and Australia |
E368885
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | allied governments |
C15050
|
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: allied governments Context triple: [governments of the United States, United Kingdom, Netherlands, and Australia, instanceOf, allied governments]
-
A.
allied communities
Allied communities are groups of distinct but cooperative populations or organizations that intentionally collaborate, share resources, and coordinate actions to advance common goals while maintaining their individual identities.
-
B.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
C.
commonwealth
A commonwealth is a political community founded for the common good, typically characterized by shared governance, mutual obligations among its members, and a focus on public welfare.
-
D.
inter-Allied military staff
A collaborative body of military officers from multiple allied nations responsible for joint strategic planning, coordination, and command of combined armed forces.
-
E.
group of national governments
chosen
A group of national governments is a collective of sovereign state authorities that coordinate policies, decisions, or actions on shared interests or issues.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 4:03 a.m.