Triple
T36938950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (1987) |
E913696
|
entity |
| Predicate | fleetAssociation |
P62262
|
FINISHED |
| Object | Canadian Pacific fleet |
—
|
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: Canadian Pacific fleet | Statement: [SS Empress of Britain (1987), fleetAssociation, Canadian Pacific fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetAssociation Context triple: [SS Empress of Britain (1987), fleetAssociation, Canadian Pacific fleet]
-
A.
fleetName
Indicates the name assigned to a particular fleet within a system or context.
-
B.
shipAssociatedWith
chosen
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
C.
fleetFocus
Indicates that attention, resources, or strategic priority are being directed toward a particular fleet within a broader operational or organizational context.
-
D.
navalAffiliation
Indicates a formal relationship in which an entity is associated with, belongs to, or operates under a particular navy or naval force.
-
E.
shipRegistry
Indicates that an entity is officially recorded or listed in a particular ship registry or registration system.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe174a508190a717d6e962a90fb7 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.