Triple
T36588284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2035) |
E902588
|
entity |
| Predicate | hasPlannedRouteType |
P86666
|
FINISHED |
| Object | transoceanic |
—
|
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: transoceanic | Statement: [SS Empress of Canada (2035), hasPlannedRouteType, transoceanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedRouteType Context triple: [SS Empress of Canada (2035), hasPlannedRouteType, transoceanic]
-
A.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
B.
hasPlannedTerminalType
Indicates that an entity is associated with a specific type of terminal that is intended or scheduled to be used in the future.
-
C.
hasPlannedLine
chosen
Indicates that an entity is associated with a specific planned route or line intended for future or scheduled use.
-
D.
hasPilgrimageRouteType
Indicates that a pilgrimage route is associated with a specific type or category of pilgrimage path.
-
E.
hasPlannedOperatorType
Indicates that an entity is associated with a specific type of operator that is intended or scheduled to perform an operation or service.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:11 p.m.