Triple
T30575125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir William Pynsent, 1st Baronet |
E778222
|
entity |
| Predicate | associatedWithTaxIssue |
P29037
|
FINISHED |
| Object | cider tax controversy |
—
|
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: cider tax controversy | Statement: [Sir William Pynsent, 1st Baronet, associatedWithTaxIssue, cider tax controversy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTaxIssue Context triple: [Sir William Pynsent, 1st Baronet, associatedWithTaxIssue, cider tax controversy]
-
A.
taxCase
Indicates a legal case or proceeding whose primary subject is taxation or tax-related disputes between parties.
-
B.
taxObligations
Indicates the duties or liabilities an entity has to pay taxes under applicable laws or regulations.
-
C.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
D.
tariffIssueContext
Indicates the contextual circumstances or factors under which a tariff is applied, discussed, or becomes relevant in a given situation.
-
E.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:22 p.m.