Triple
T26748216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Lancastria |
E674459
|
entity |
| Predicate | locationOfFinalVoyage |
P96320
|
FINISHED |
| Object | Saint-Nazaire roadstead |
—
|
NE NERFINISHED |
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: Saint-Nazaire roadstead | Statement: [RMS Lancastria, locationOfFinalVoyage, Saint-Nazaire roadstead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFinalVoyage Context triple: [RMS Lancastria, locationOfFinalVoyage, Saint-Nazaire roadstead]
-
A.
destinationOnFinalVoyage
chosen
Indicates the place where an entity ultimately arrived or was intended to arrive on its final journey or last voyage.
-
B.
statusDuringFinalVoyage
Indicates the role, condition, or state an entity held specifically during its final voyage.
-
C.
destinationOfVoyageTo
Indicates the endpoint location that a particular voyage or journey is directed toward or arrives at.
-
D.
departurePortOnFinalVoyage
Indicates the port from which an entity (such as a vessel) last departed on its final recorded voyage.
-
E.
laterOutcomeOfVoyage
Indicates that one event, state, or outcome occurs as a subsequent result or later phase of a specified voyage.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 27, 2026, 3:52 a.m.