Triple
T38041917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2050) |
E949506
|
entity |
| Predicate | shipbuilderHeadquartersLocation |
P178893
|
FINISHED |
| Object | Clydebank |
—
|
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: Clydebank | Statement: [SS Empress of Canada (2050), shipbuilderHeadquartersLocation, Clydebank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipbuilderHeadquartersLocation Context triple: [SS Empress of Canada (2050), shipbuilderHeadquartersLocation, Clydebank]
-
A.
shipbuilderLocation
chosen
Indicates the location where a shipbuilder is based or operates.
-
B.
shipbuilder
Indicates that one entity is the builder or constructor of a ship associated with another entity.
-
C.
hasShipyardIn
Indicates that an entity operates or possesses a shipyard located in a specified place.
-
D.
shipbuilderType
Indicates the specific kind or category of shipbuilder associated with an entity (e.g., by role, specialization, or organizational type).
-
E.
shipyardLocatedOn
Indicates that a shipyard is situated on or within the geographic area of a specified landmass, coastline, or body of water.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.