Triple
T14830900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Terror |
E348698
|
entity |
| Predicate | hullReinforcement |
P115998
|
FINISHED |
| Object | ice-strengthened hull |
—
|
LITERAL 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: ice-strengthened hull | Statement: [HMS Terror, hullReinforcement, ice-strengthened hull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullReinforcement Context triple: [HMS Terror, hullReinforcement, ice-strengthened hull]
-
A.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
-
B.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
-
C.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
D.
hullPreservation
Indicates the extent to which an object’s outer structure or surface has been maintained intact and protected from damage or deterioration.
-
E.
enhancedArmament
Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
- F. None of above. chosen
Provenance (4 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0748eec8190a39c94024c3a3e3e |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:52 a.m.