Triple
T34272401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (2007) |
E879353
|
entity |
| Predicate | hasCrewFacilities |
P121590
|
FINISHED |
| Object | crew cabins |
—
|
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: crew cabins | Statement: [SS Empress of Britain (2007), hasCrewFacilities, crew cabins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewFacilities Context triple: [SS Empress of Britain (2007), hasCrewFacilities, crew cabins]
-
A.
hasCruiseFacilities
Indicates that a location or entity provides facilities or infrastructure to support cruise ships or cruise-related activities.
-
B.
hasPassengerAmenity
chosen
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
C.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
D.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
-
E.
hasDockingFacilities
Indicates that one entity provides or is equipped with docking facilities for another entity.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:56 a.m.