Triple
T37034832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1986) |
E916602
|
entity |
| Predicate | operatedInServiceType |
P31751
|
FINISHED |
| Object | international passenger service |
—
|
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: international passenger service | Statement: [SS Empress of Canada (1986), operatedInServiceType, international passenger service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInServiceType Context triple: [SS Empress of Canada (1986), operatedInServiceType, international passenger service]
-
A.
operatedFreightServiceIn
Indicates that an entity operated a freight transportation service within or across the specified geographic area or route.
-
B.
transitSystemTypeOperated
Indicates the type of transit system that an operator runs or manages.
-
C.
operatedPassengerServices
chosen
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
D.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
E.
modeOfService
Indicates the manner, method, or channel through which a service is delivered or provided.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01ed1790148190b08c1dba53de4371 |
completed | May 11, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_6a01e9c20798819085760b377dc7b3fa |
completed | May 11, 2026, 2:37 p.m. |
Created at: May 3, 2026, 4:14 p.m.