Triple
T5217204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Hampshire |
E117780
|
entity |
| Predicate | wreckProtection |
P62092
|
FINISHED |
| Object | protected site under UK law |
—
|
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: protected site under UK law | Statement: [HMS Hampshire, wreckProtection, protected site under UK law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wreckProtection Context triple: [HMS Hampshire, wreckProtection, protected site under UK law]
-
A.
wreckSalvaged
Indicates that a previously wrecked object or structure has been recovered or salvaged from its damaged or sunken state.
-
B.
containsWreck
Indicates that one entity includes or holds within it the remains or wreckage of another entity.
-
C.
wreckDepth
Indicates the depth at which a wreck is located below the water surface.
-
D.
shipwreckUse
Indicates that an entity makes use of, interacts with, or derives benefit from a shipwreck.
-
E.
wreckDiscovery
Indicates that an entity discovers, finds, or identifies a wreck (such as a ruined or destroyed object, vehicle, or structure).
- 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_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. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.