Triple
T36861002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1982) |
E910934
|
entity |
| Predicate | builtByCompanyType |
P4022
|
FINISHED |
| Object | Scottish shipbuilding firm |
—
|
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: Scottish shipbuilding firm | Statement: [SS Empress of Canada (1982), builtByCompanyType, Scottish shipbuilding firm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtByCompanyType Context triple: [SS Empress of Canada (1982), builtByCompanyType, Scottish shipbuilding firm]
-
A.
oftenBuiltBy
Indicates that something is frequently or commonly constructed or created by a particular agent or type of agent.
-
B.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
C.
alsoManufacturedBy
Indicates that an item or product is produced by an additional manufacturer beyond the primary or previously mentioned one.
-
D.
builtType
Indicates the structural or construction type characterizing how something is built or formed.
-
E.
manufacturedBy
chosen
Indicates that an item or product is produced or created by a specific manufacturer or maker.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.