Triple
T3606103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Canberra |
E76374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Australian Navy warship |
C13461
|
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 warship Context triple: [HMAS Canberra, instanceOf, Royal Australian Navy warship]
-
A.
Royal New Zealand Navy ship
A Royal New Zealand Navy ship is a commissioned naval vessel operated by the Royal New Zealand Navy to perform maritime defense, security, and support roles for New Zealand and its interests.
-
B.
Royal Navy warship
A Royal Navy warship is a commissioned naval vessel of the United Kingdom designed, armed, and operated for maritime defense, power projection, and support of national interests at sea.
-
C.
Royal Navy destroyer
A Royal Navy destroyer is a fast, maneuverable warship designed for fleet escort, anti-submarine, anti-air, and surface warfare operations within the United Kingdom’s naval forces.
-
D.
United States Navy ship
A United States Navy ship is a commissioned naval vessel operated by the U.S. Navy, designed, equipped, and crewed to perform military, logistical, and support missions at sea and in littoral environments.
-
E.
Imperial Japanese Navy warship
An Imperial Japanese Navy warship is a naval combat vessel that served under Japan’s maritime military forces, primarily during the late 19th and early 20th centuries, designed and equipped for roles such as fleet engagement, escort, and power projection.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.