Triple
T8740629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revenue Act 1766 |
E207489
|
entity |
| Predicate | typeOfTaxation |
P3166
|
FINISHED |
| Object | customs duties |
—
|
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: customs duties | Statement: [Revenue Act 1766, typeOfTaxation, customs duties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTaxation Context triple: [Revenue Act 1766, typeOfTaxation, customs duties]
-
A.
taxRegime
Indicates the system or structure of taxation that governs how taxes are assessed, collected, and applied within a particular context or jurisdiction.
-
B.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
D.
typeOfTaxpayerCovered
Indicates the category or kind of taxpayer to which a particular rule, obligation, or provision applies.
-
E.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d4a0cf481909c770cb39fd00fcd |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:38 p.m.