Triple
T9747622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Govan shipyard |
E236353
|
entity |
| Predicate | employerInSector |
P62538
|
FINISHED |
| Object | skilled shipyard workers |
—
|
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: skilled shipyard workers | Statement: [Govan shipyard, employerInSector, skilled shipyard workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerInSector Context triple: [Govan shipyard, employerInSector, skilled shipyard workers]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
hasOccupationSector
chosen
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
C.
employerType
Indicates the classification or category of an employer in relation to the entity (e.g., public, private, nonprofit, self-employed).
-
D.
targetCompanyIndustry
Indicates that a company operates within or is associated with a specified industry sector.
-
E.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f677830819096d388b9c798ecd5 |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.