Triple
T16458419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gull Force |
E399742
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Australian Army infantry force |
C15162
|
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: Australian Army infantry force Context triple: [Gull Force, instanceOf, Australian Army infantry force]
-
A.
Australian Army formation
An Australian Army formation is a structured military organization composed of multiple units and sub-units, established to plan, coordinate, and conduct land operations under a unified command within the Australian Army.
-
B.
component of the Australian Army
chosen
A component of the Australian Army is an organizational subdivision—such as a unit, formation, corps, or support element—that contributes specific capabilities and functions to the Army’s overall mission and operations.
-
C.
Australian Defence Force position
An Australian Defence Force position represents a specific role or appointment within the ADF’s organizational structure, defined by its responsibilities, rank requirements, and placement in the command hierarchy.
-
D.
Royal Australian Air Force unit
A Royal Australian Air Force unit is an organizational entity within the RAAF, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support roles in air and space power.
-
E.
New Zealand Army formation
A New Zealand Army formation is an organized military unit or grouping, such as a brigade or division, composed of personnel and equipment structured to conduct land operations under a unified command.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.