Triple
T13326118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMC Ships |
E317445
|
entity |
| Predicate | hasPrefix |
P66954
|
FINISHED |
| Object | HMCS |
E994055
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: HMCS | Statement: [HMC Ships, hasPrefix, HMCS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HMCS Context triple: [HMC Ships, hasPrefix, HMCS]
-
A.
HMCS
chosen
HMCS is the ship prefix used to designate vessels of the Royal Canadian Navy, standing for "Her Majesty's Canadian Ship" (or "His Majesty's Canadian Ship").
-
B.
HMCS Stadacona
HMCS Stadacona is a major Royal Canadian Navy shore establishment and administrative base located in Halifax, Nova Scotia.
-
C.
HMCS Windsor
HMCS Windsor is a Canadian Royal Navy diesel-electric attack submarine of the Victoria class, used primarily for coastal defense, surveillance, and training operations.
-
D.
HMCS Victoria
HMCS Victoria is a Canadian Royal Navy diesel-electric attack submarine that serves as the lead vessel of the Victoria-class.
-
E.
HMCS Haida
HMCS Haida is a preserved Royal Canadian Navy Tribal-class destroyer famed for its World War II service and now serves as a museum ship in Hamilton, Ontario.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992d3b0881909732fbb8db98e44c |
completed | April 11, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7266f70088190a518e273af507361 |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:30 p.m.