Triple
T19265413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiers État |
E481761
|
entity |
| Predicate | taxBurden |
P135344
|
FINISHED |
| Object | main taxpayer under the Ancien Régime |
—
|
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: main taxpayer under the Ancien Régime | Statement: [Tiers État, taxBurden, main taxpayer under the Ancien Régime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxBurden Context triple: [Tiers État, taxBurden, main taxpayer under the Ancien Régime]
-
A.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
C.
taxRate
Indicates the percentage or proportion of a taxable amount that is imposed as tax in a given context.
-
D.
taxFunction
Indicates the rule or calculation method used to determine the amount of tax applied to a given input (such as income, price, or transaction).
-
E.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8ca2e88190baad3b6c199ee036 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.