Triple
T36258057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (1931) |
E891997
|
entity |
| Predicate | voyageAtSinking |
P166213
|
FINISHED |
| Object | troopship voyage from Cape Town to the United Kingdom |
—
|
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: troopship voyage from Cape Town to the United Kingdom | Statement: [SS Empress of Britain (1931), voyageAtSinking, troopship voyage from Cape Town to the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageAtSinking Context triple: [SS Empress of Britain (1931), voyageAtSinking, troopship voyage from Cape Town to the United Kingdom]
-
A.
voyageStatusAtSinking
Indicates the status or phase of a voyage that a vessel was in at the time it sank.
-
B.
routeAtTimeOfSinking
chosen
Indicates the specific route an entity (such as a vessel) was following at the time it sank.
-
C.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
-
D.
missionAtTimeOfSinking
Indicates that a vessel was engaged in a specific mission or operational role at the time it sank.
-
E.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fece288190bd538ba5391d45e7 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.