Triple
T38453461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1983) |
E912239
|
entity |
| Predicate | builtByRenownedShipbuilder |
P159340
|
FINISHED |
| Object | John Brown & Company |
—
|
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: John Brown & Company | Statement: [SS Empress of Canada (1983), builtByRenownedShipbuilder, John Brown & Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtByRenownedShipbuilder Context triple: [SS Empress of Canada (1983), builtByRenownedShipbuilder, John Brown & Company]
-
A.
shipbuilder
chosen
Indicates that one entity is the builder or constructor of a ship associated with another entity.
-
B.
shipbuilderType
Indicates the specific kind or category of shipbuilder associated with an entity (e.g., by role, specialization, or organizational type).
-
C.
notableVesselBuilt
Indicates that a particular vessel was constructed by or for the subject and is notable or significant in that context.
-
D.
associatedWithShipbuilder
Indicates a relationship where an entity is connected or linked in some relevant capacity to a shipbuilder.
-
E.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.