Triple
T34064193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2025) |
E873574
|
entity |
| Predicate | hasBuilderType |
P187075
|
FINISHED |
| Object | historic shipbuilding company |
—
|
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: historic shipbuilding company | Statement: [SS Empress of Canada (2025), hasBuilderType, historic shipbuilding company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuilderType Context triple: [SS Empress of Canada (2025), hasBuilderType, historic shipbuilding company]
-
A.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
B.
hasBuilderPredecessor
Indicates that one builder entity temporally or logically precedes another in a construction or creation process.
-
C.
belongsToBuildingType
Indicates that something is classified as being of a particular building type.
-
D.
hasGeneratorType
Indicates that an entity is associated with or uses a specific type or category of generator.
-
E.
hasBuildTool
Indicates that an entity uses or is associated with a specific tool or system for building, compiling, or assembling software or other artifacts.
- F. None of above. chosen
Provenance (4 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 1, 2026, 1:52 a.m.