Triple
T35177230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port McNicoll |
E1015740
|
entity |
| Predicate | servedByShipLine |
P1293
|
FINISHED |
| Object | Canadian Pacific Steamships |
—
|
NE NERFINISHED |
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 Steamships | Statement: [Port McNicoll, servedByShipLine, Canadian Pacific Steamships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByShipLine Context triple: [Port McNicoll, servedByShipLine, Canadian Pacific Steamships]
-
A.
servedShip
Indicates that one entity performed service or duty aboard, or in direct support of, a particular ship.
-
B.
ownedShippingLine
Indicates that one entity possessed legal ownership or controlling interest in a particular shipping line.
-
C.
shippingLine
Indicates a relationship where an entity is associated with, or transported via, a particular shipping line or carrier service.
-
D.
servedByLine
chosen
Indicates that a transportation stop, station, or location is provided service by a specific transit line.
-
E.
shipCompany
Indicates that one entity is the shipping company responsible for transporting goods or providing shipping services 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:02 p.m.