Triple
T14863172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMT Dunera |
E349548
|
entity |
| Predicate | voyageCharacterization |
P24304
|
FINISHED |
| Object | harsh |
—
|
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: harsh | Statement: [HMT Dunera, voyageCharacterization, harsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageCharacterization Context triple: [HMT Dunera, voyageCharacterization, harsh]
-
A.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
B.
voyageWith
Indicates that two or more entities travel together on the same journey or trip, sharing a common route or voyage.
-
C.
voyageType
chosen
Indicates the specific category or nature of a journey or trip that an entity undertakes.
-
D.
inspiredVoyage
Indicates that one entity’s ideas, actions, or example motivated another entity to undertake a particular journey or expedition.
-
E.
featuresVessel
Indicates that one entity includes, presents, or prominently displays a particular vessel as part of its composition, content, or configuration.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded574d0ec8190a6afed672ba6c2f9 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.