Triple
T14101510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blairmore Holdings |
E339391
|
entity |
| Predicate | usedTaxStrategy |
P39307
|
FINISHED |
| Object | non-resident status for UK tax purposes |
—
|
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: non-resident status for UK tax purposes | Statement: [Blairmore Holdings, usedTaxStrategy, non-resident status for UK tax purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTaxStrategy Context triple: [Blairmore Holdings, usedTaxStrategy, non-resident status for UK tax purposes]
-
A.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
B.
usedInTaxPayments
Indicates that something is employed or applied as part of making or fulfilling tax payments.
-
C.
taxFunction
Indicates the rule or calculation method used to determine the amount of tax applied to a given input (such as income, price, or transaction).
-
D.
effectOnTaxes
chosen
Indicates how one entity or action changes, influences, or determines the amount, structure, or treatment of taxes for another entity or situation.
-
E.
taxStage
Indicates the specific phase or step an entity is in within a tax-related process or lifecycle.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fbbf0b08190ba1ea3657d6db005 |
completed | April 14, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.