Triple
T32181463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Clyde Shipbuilders |
E821991
|
entity |
| Predicate | aimOfWorkIn |
P64674
|
FINISHED |
| Object | to keep yards open and secure jobs |
—
|
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: to keep yards open and secure jobs | Statement: [Upper Clyde Shipbuilders, aimOfWorkIn, to keep yards open and secure jobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfWorkIn Context triple: [Upper Clyde Shipbuilders, aimOfWorkIn, to keep yards open and secure jobs]
-
A.
aimOfWorks
Indicates that certain works (such as projects, activities, or creations) are directed toward or intended to achieve a particular aim or purpose.
-
B.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
purposeOfWork
Indicates that one entity is the intended goal, function, or objective that motivates or justifies the work performed by another entity.
-
D.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6baaefb9c8190a25ef9628c09e36f |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:34 a.m.