Triple
T31293873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smoothfield Holding Limited |
E798021
|
entity |
| Predicate | ownsSharesIn |
P121928
|
FINISHED |
| Object | Mitchells & Butlers plc |
—
|
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: Mitchells & Butlers plc | Statement: [Smoothfield Holding Limited, ownsSharesIn, Mitchells & Butlers plc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownsSharesIn Context triple: [Smoothfield Holding Limited, ownsSharesIn, Mitchells & Butlers plc]
-
A.
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.
-
B.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
C.
hasShareholdersFrom
Indicates that an entity has shareholders who originate from or are associated with a specified country, region, or organization.
-
D.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
E.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.