Triple
T38522852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2042) |
E922535
|
entity |
| Predicate | hasPassengerShipType |
P187006
|
FINISHED |
| Object | cruise liner (conceptual) |
—
|
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: cruise liner (conceptual) | Statement: [SS Empress of Canada (2042), hasPassengerShipType, cruise liner (conceptual)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerShipType Context triple: [SS Empress of Canada (2042), hasPassengerShipType, cruise liner (conceptual)]
-
A.
isCapitalShip
Indicates that the subject vessel is classified as a capital ship, i.e., a primary, large, and heavily armed warship within a fleet.
-
B.
hasShipTypeCharacteristic
Indicates that a ship possesses a specific characteristic or property related to its type.
-
C.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
D.
passengerVessel
chosen
Indicates that one entity is a vessel whose primary function is to carry passengers.
-
E.
hasBoatOrShip
Indicates that an entity possesses, owns, or is associated with a boat or ship.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
Created at: May 3, 2026, 4:32 p.m.