Triple
T5217207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Hampshire |
E117780
|
entity |
| Predicate | sinkingDuring |
P18834
|
FINISHED |
| Object | World War I naval operations around Orkney |
—
|
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: World War I naval operations around Orkney | Statement: [HMS Hampshire, sinkingDuring, World War I naval operations around Orkney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinkingDuring Context triple: [HMS Hampshire, sinkingDuring, World War I naval operations around Orkney]
-
A.
sunkDuring
chosen
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
B.
sunk
Indicates that one entity caused another entity to go below the surface of a liquid, typically water, so that it is submerged or destroyed.
-
C.
sankOn
Indicates that one entity moved downward and became submerged or lower in level relative to another entity or reference point.
-
D.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
E.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
- F. None of above.
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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a95abdc8190b0babd79cea1360e |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.