Triple
T34750659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2060) |
E1001765
|
entity |
| Predicate | primaryFunctionAfterWar |
P85328
|
FINISHED |
| Object | resumed civilian passenger service |
—
|
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: resumed civilian passenger service | Statement: [SS Empress of Canada (2060), primaryFunctionAfterWar, resumed civilian passenger service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionAfterWar Context triple: [SS Empress of Canada (2060), primaryFunctionAfterWar, resumed civilian passenger service]
-
A.
postWarFunction
chosen
Indicates how something operated, was used, or what role it served in the period following a war.
-
B.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
-
C.
primaryUseLateWar
Indicates that something was used primarily during the later phase of a war, rather than in its early or middle stages.
-
D.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
E.
statusPostWar
Indicates the condition or situation of an entity after a war has ended.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.