Triple
T19233876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subahdar of Balkh |
E480940
|
entity |
| Predicate | fiscalDuties |
P135287
|
FINISHED |
| Object | assessment of land revenue in Balkh |
—
|
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: assessment of land revenue in Balkh | Statement: [Subahdar of Balkh, fiscalDuties, assessment of land revenue in Balkh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalDuties Context triple: [Subahdar of Balkh, fiscalDuties, assessment of land revenue in Balkh]
-
A.
taxObligations
Indicates the duties or liabilities an entity has to pay taxes under applicable laws or regulations.
-
B.
regulatesTariffs
Indicates that one entity has authority to control, set, or adjust the tariffs imposed on another entity or on certain transactions.
-
C.
averageTariffRateOnDutiableImports
Indicates the average tariff rate applied specifically to imported goods that are subject to customs duties.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
fiscalInstrument
Indicates a financial tool or mechanism used to manage, allocate, or influence monetary resources, obligations, or economic activity.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faeb53988190b83afee9974058c6 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:26 p.m.