Triple
T31076332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Anzac (fictional cruiser) |
E791974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional Royal Australian Navy ship |
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: fictional Royal Australian Navy ship Context triple: [HMAS Anzac (fictional cruiser), instanceOf, fictional Royal Australian Navy ship]
-
A.
fictional ship
A fictional ship is an imagined seafaring or spacefaring vessel, defined by its design, purpose, and narrative role within a story’s setting.
-
B.
fictional Royal Navy submarine
A fictional Royal Navy submarine is an imagined undersea warship serving in Britain’s naval fleet, typically depicted conducting covert patrols, intelligence gathering, and combat missions beneath the ocean’s surface.
-
C.
Royal Australian Navy warship
chosen
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 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.
-
E.
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.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.