Triple
T25842518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEA 1180 Phase 1 |
E650974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Navy procurement project |
C50788
|
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 procurement project Context triple: [SEA 1180 Phase 1, instanceOf, Royal Australian Navy procurement project]
-
A.
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.
-
B.
Royal Navy programme
A Royal Navy programme is an organized initiative or plan undertaken by the Royal Navy to develop, maintain, or enhance its capabilities, operations, personnel, or infrastructure over a defined period.
-
C.
Royal Australian Navy formation
A Royal Australian Navy formation is an organized grouping of naval vessels, units, or personnel structured for operational, administrative, or ceremonial purposes within the Royal Australian Navy.
-
D.
Anzac-class frigate
The Anzac-class frigate is a class of modern, multi-role warships operated by the Royal Australian Navy and Royal New Zealand Navy, designed primarily for anti-submarine and anti-surface warfare, as well as air defense and patrol duties.
-
E.
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.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:50 a.m.