Triple
T38563014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2044) |
E928131
|
entity |
| Predicate | hasPassengerCabins |
P12453
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SS Empress of Canada (2044), hasPassengerCabins, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerCabins Context triple: [SS Empress of Canada (2044), hasPassengerCabins, yes]
-
A.
hasCabinClass
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
-
B.
capacityPerCabin
Indicates the number of occupants or units that each individual cabin is designed or allowed to hold.
-
C.
hasCabins
chosen
Indicates that an entity possesses or includes one or more cabins as part of its structure or facilities.
-
D.
cruiseCapability
Indicates the ability of an entity to travel or operate in a steady, sustained cruising mode under its own power.
-
E.
cabinClassAbove
Indicates that one cabin class is ranked higher or more premium than another in a class hierarchy.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4:32 p.m.