Triple
T4542328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vannin |
E107562
|
entity |
| Predicate | hasOwnTaxSystem |
P57593
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Vannin, hasOwnTaxSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnTaxSystem Context triple: [Vannin, hasOwnTaxSystem, true]
-
A.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
B.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
C.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
D.
hasSpecialTaxArrangements
Indicates that an entity is subject to or benefits from non-standard or preferential tax treatment compared to the usual tax rules.
-
E.
typeOfTaxpayerCovered
Indicates the category or kind of taxpayer to which a particular rule, obligation, or provision applies.
- F. None of above. chosen
Provenance (4 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d3be988190bf118c4a87415613 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:04 p.m.