Triple
T36588254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1976) |
E902587
|
entity |
| Predicate | passengerVessel |
P187006
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SS Empress of Canada (1976), passengerVessel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerVessel Context triple: [SS Empress of Canada (1976), passengerVessel, true]
-
A.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
B.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
C.
shipName
Indicates the name assigned to a specific ship in the relationship.
-
D.
expeditionShip
Indicates a relationship where a ship is designated or used specifically for conducting an expedition or exploratory mission.
-
E.
isMotorVessel
Indicates that the subject entity is a motor-powered vessel, typically propelled by an engine rather than by sails or oars.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.