Triple
T33532528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotstoun, Glasgow |
E858832
|
entity |
| Predicate | hasShipbuildingHeritage |
P20564
|
FINISHED |
| Object | yards along the River Clyde |
—
|
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: yards along the River Clyde | Statement: [Scotstoun, Glasgow, hasShipbuildingHeritage, yards along the River Clyde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipbuildingHeritage Context triple: [Scotstoun, Glasgow, hasShipbuildingHeritage, yards along the River Clyde]
-
A.
hasMaritimeHeritage
chosen
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
B.
hasShipyardIn
Indicates that an entity operates or possesses a shipyard located in a specified place.
-
C.
shipbuildingActivity
Indicates the activity or process of constructing, assembling, or significantly modifying ships or large watercraft.
-
D.
shipbuilder
Indicates that one entity is the builder or constructor of a ship associated with another entity.
-
E.
shipyardFormerName
Indicates that a shipyard previously operated under a different name, specifying what that former name was.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:39 a.m.