Triple
T28297030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MV Derbyshire |
E713596
|
entity |
| Predicate | routeAtTimeOfSinking |
P166213
|
FINISHED |
| Object | from Canada to Japan |
—
|
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: from Canada to Japan | Statement: [MV Derbyshire, routeAtTimeOfSinking, from Canada to Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAtTimeOfSinking Context triple: [MV Derbyshire, routeAtTimeOfSinking, from Canada to Japan]
-
A.
missionAtTimeOfSinking
Indicates that a vessel was engaged in a specific mission or operational role at the time it sank.
-
B.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
-
C.
flagAtTimeOfSinking
Indicates the national flag under which a vessel was registered or sailing at the specific time it sank.
-
D.
legalStatusAtTimeOfSinking
Indicates the legal status or condition that applied to an entity at the specific time it sank.
-
E.
voyageStatusAtSinking
Indicates the status or phase of a voyage that a vessel was in at the time it sank.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 11:32 p.m.