Triple
T8887146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Australian Naval Task Force 74 |
E211559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Navy formation |
C25238
|
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: Royal Australian Navy formation Context triple: [Royal Australian Naval Task Force 74, instanceOf, Royal Australian Navy formation]
-
A.
Royal Australian Air Force formation
A Royal Australian Air Force formation is an organizational grouping of RAAF units, aircraft, and personnel structured to conduct specific operational, training, or support roles under a unified command.
-
B.
Royal Canadian Navy formation
A Royal Canadian Navy formation is an organized operational grouping of naval units, personnel, and resources structured under a unified command to conduct maritime missions and support national defense objectives.
-
C.
Royal Australian Navy warship
A Royal Australian Navy warship is a commissioned naval vessel operated by Australia’s maritime defense force, designed and equipped for roles such as combat, patrol, escort, surveillance, and support in national and allied operations.
-
D.
Royal Australian Navy shore establishment
A Royal Australian Navy shore establishment is a land-based facility that supports naval operations through administration, training, logistics, maintenance, and other essential services.
-
E.
U.S. Navy formation
A U.S. Navy formation is an organized arrangement of naval vessels or aircraft maneuvering together under a unified command to achieve tactical, operational, or ceremonial objectives at sea or in the air.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:53 p.m.