Triple
T38563028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2044) |
E928131
|
entity |
| Predicate | hasCargoHolds |
P148162
|
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), hasCargoHolds, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCargoHolds Context triple: [SS Empress of Canada (2044), hasCargoHolds, yes]
-
A.
hasCargoHold
chosen
Indicates that something possesses a dedicated space or compartment for storing or transporting cargo.
-
B.
hasCargoAccess
Indicates that an entity has the ability or permission to access a designated cargo area or its contents.
-
C.
isPressurizedCargoCarrier
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
cargoHoldVolume
Indicates the total internal volume available within a cargo hold for storing goods or materials.
- 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_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
Created at: May 3, 2026, 4:32 p.m.