Triple

T32181446
Position Surface form Disambiguated ID Type / Status
Subject Upper Clyde Shipbuilders E821991 entity
Predicate hadShareholder P121928 FINISHED
Object British government 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: British government | Statement: [Upper Clyde Shipbuilders, hadShareholder, British government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadShareholder
Context triple: [Upper Clyde Shipbuilders, hadShareholder, British government]
  • A. hasShareholdersFrom
    Indicates that an entity has shareholders who originate from or are associated with a specified country, region, or organization.
  • B. hasShareholderAgreementWith
    Indicates that two or more parties are bound by a shareholder agreement governing their rights and obligations regarding shares in a company.
  • C. isShareholderOf chosen
    Indicates that one entity owns shares or equity in another entity, giving it a financial stake and certain associated rights in that entity.
  • D. majorShareholderOf
    Indicates that one entity owns a controlling or significantly large portion of another entity’s shares or equity.
  • E. minorityShareholder
    Indicates that one entity holds a non-controlling, less-than-majority ownership stake in 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.