Triple
T3889149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMHS Britannic |
E88014
|
entity |
| Predicate | registrationPrefix |
P7142
|
FINISHED |
| Object |
HMHS
HMHS is the registration prefix used to designate British hospital ships, standing for "His/Her Majesty's Hospital Ship."
|
E397889
|
NE FINISHED |
How this triple was built (4 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: HMHS | Statement: [HMHS Britannic, registrationPrefix, HMHS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HMHS Context triple: [HMHS Britannic, registrationPrefix, HMHS]
-
A.
HMS
HMS is the ship prefix used for vessels of the British Royal Navy, standing for "His (or Her) Majesty's Ship."
-
B.
HMT
HMT is the commonly used abbreviation for HM Treasury, the United Kingdom government department responsible for economic and financial policy.
-
C.
HM
HM is a prefix used for classes and APIs in Apple's HomeKit framework, which enables communication and control of smart home accessories on iOS and other Apple platforms.
-
D.
HM
HM is an abbreviation commonly used as a formal title for a reigning queen or king, standing for "Her Majesty" or "His Majesty."
-
E.
HMS Eskimo
HMS Eskimo was a Royal Navy destroyer that saw extensive service during the Second World War, including major operations in the Arctic, Mediterranean, and Normandy landings.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: HMHS Triple: [HMHS Britannic, registrationPrefix, HMHS]
Generated description
HMHS is the registration prefix used to designate British hospital ships, standing for "His/Her Majesty's Hospital Ship."
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: HMHS Target entity description: HMHS is the registration prefix used to designate British hospital ships, standing for "His/Her Majesty's Hospital Ship."
-
A.
HMS
HMS is the ship prefix used for vessels of the British Royal Navy, standing for "His (or Her) Majesty's Ship."
-
B.
HMT
HMT is the commonly used abbreviation for HM Treasury, the United Kingdom government department responsible for economic and financial policy.
-
C.
HM
HM is a prefix used for classes and APIs in Apple's HomeKit framework, which enables communication and control of smart home accessories on iOS and other Apple platforms.
-
D.
HM
HM is an abbreviation commonly used as a formal title for a reigning queen or king, standing for "Her Majesty" or "His Majesty."
-
E.
HMS Eskimo
HMS Eskimo was a Royal Navy destroyer that saw extensive service during the Second World War, including major operations in the Arctic, Mediterranean, and Normandy landings.
- F. None of above. chosen
Provenance (5 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecaee7148190ada451ccfc6582ee |
completed | March 9, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51c8f299c8190a6a53ec59837b402 |
completed | March 14, 2026, 8:30 a.m. |
| NEDg | Description generation | batch_69b51d51e52881908f798b12ee123d69 |
completed | March 14, 2026, 8:33 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b51dba68fc8190b02b0ca47f4f7803 |
completed | March 14, 2026, 8:35 a.m. |
Created at: March 9, 2026, 3:21 p.m.