Triple
T15439479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oil and Gas Tax Administration in Alaska |
E369858
|
entity |
| Predicate | usesTaxType |
P3166
|
FINISHED |
| Object | production tax |
—
|
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: production tax | Statement: [Oil and Gas Tax Administration in Alaska, usesTaxType, production tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTaxType Context triple: [Oil and Gas Tax Administration in Alaska, usesTaxType, production tax]
-
A.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
usesTariffSystem
Indicates that one entity applies or operates under a tariff-based system for pricing, taxation, or fees in its interactions or transactions.
-
C.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eddf258819082679970b7d2b6af |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.