Triple
T28178622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inconfidência Mineira |
E715963
|
entity |
| Predicate | taxationIssue |
P144624
|
FINISHED |
| Object | derrama |
—
|
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: derrama | Statement: [Inconfidência Mineira, taxationIssue, derrama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxationIssue Context triple: [Inconfidência Mineira, taxationIssue, derrama]
-
A.
taxCase
Indicates a legal case or proceeding whose primary subject is taxation or tax-related disputes between parties.
-
B.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
-
D.
taxationGrievance
chosen
Indicates a relationship where an entity holds a complaint, objection, or sense of unfairness regarding the taxes imposed or the taxation system.
-
E.
taxBurden
Indicates the extent to which an entity is obligated to pay taxes, typically reflecting the level or share of tax liability it bears.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64280c02c819085919ec4918b2950 |
completed | May 2, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:18 p.m.