Triple
T24229656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABDA naval forces in the Netherlands East Indies |
E601692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combined Allied naval command |
C33841
|
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: combined Allied naval command Context triple: [ABDA naval forces in the Netherlands East Indies, instanceOf, combined Allied naval command]
-
A.
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.
-
B.
Royal Navy operational command
A Royal Navy operational command is an organizational unit responsible for planning, directing, and controlling naval forces and operations within a defined area or functional domain.
-
C.
Royal Navy command position
A Royal Navy command position is an official role within the naval hierarchy responsible for directing ships, fleets, or shore establishments and overseeing personnel, operations, and strategic decision-making.
-
D.
Allied air force
Allied air force: The collective aerial military forces of nations united in a coalition, coordinating air operations to achieve shared strategic and tactical objectives in conflict.
-
E.
inter-Allied military staff
chosen
A collaborative body of military officers from multiple allied nations responsible for joint strategic planning, coordination, and command of combined armed forces.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 18, 2026, 12:01 a.m.