Triple
T7808623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OTR |
E180620
|
entity |
| Predicate | collectsTaxType |
P3166
|
FINISHED |
| Object | individual income 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: individual income tax | Statement: [OTR, collectsTaxType, individual income tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsTaxType Context triple: [OTR, collectsTaxType, individual income tax]
-
A.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
C.
taxCollectorFor
Indicates that one entity is responsible for collecting taxes on behalf of another entity, such as a government, organization, or jurisdiction.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
introducedTaxType
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:36 p.m.