Triple
T30984005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland Group Holdings (post‑Baugur restructuring) |
E789468
|
entity |
| Predicate | roleInHouseOfFraser |
P200519
|
FINISHED |
| Object | controlling 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: controlling shareholder | Statement: [Highland Group Holdings (post‑Baugur restructuring), roleInHouseOfFraser, controlling shareholder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHouseOfFraser Context triple: [Highland Group Holdings (post‑Baugur restructuring), roleInHouseOfFraser, controlling shareholder]
-
A.
effectOnHouseOfFraser
Indicates the impact or consequences that something has on House of Fraser.
-
B.
roleOnDowntonAbbey
Indicates that one entity portrays or has a specific role or character in the television series "Downton Abbey" in relation to the other entity.
-
C.
roleInNappilyEverAfter
Indicates that an entity has a role or participation in the work "Nappily Ever After."
-
D.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
E.
roleInFronde
Indicates that an entity participated in or held a specific role within the historical conflict known as the Fronde.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
| PDg | Predicate description generation | batch_69ff935f48808190aa6f4834f59d45b8 |
completed | May 9, 2026, 8:04 p.m. |
Created at: April 29, 2026, 8:55 p.m.