Triple

T31293878
Position Surface form Disambiguated ID Type / Status
Subject Smoothfield Holding Limited E798021 entity
Predicate roleInMitchellsAndButlers P200753 FINISHED
Object significant shareholder 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: significant shareholder | Statement: [Smoothfield Holding Limited, roleInMitchellsAndButlers, significant shareholder]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInMitchellsAndButlers
Context triple: [Smoothfield Holding Limited, roleInMitchellsAndButlers, significant shareholder]
  • A. roleAtFoursquare
    Indicates the specific role or position an entity holds at Foursquare.
  • B. roleInTheGrandBudapestHotel
    Indicates that an entity has a specific role or part in the context of "The Grand Budapest Hotel" (such as a character, performer, or production role).
  • C. roleInBalmain
    Indicates that an entity holds or has held a specific role or position within the Balmain fashion house or brand.
  • D. roleAtStrawberryHill
    Indicates that an entity holds or held a specific role or position at Strawberry Hill.
  • E. roleInMATE
    Indicates that an entity participates in a MATE (Modeling and Analysis of Telecommunication Systems) context with a specific functional or contextual role.
  • F. None of above. chosen

Provenance (4 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_69f224dfde288190af313f3c221c857e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69ffab5adf2c819084700c5ea34615bf completed May 9, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69ffaabffa208190b5214ca17cc8a5ea completed May 9, 2026, 9:44 p.m.
PDg Predicate description generation batch_69ffab59fe408190b72f13016de9953c completed May 9, 2026, 9:47 p.m.
Created at: April 29, 2026, 9:14 p.m.