Triple
T27644131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal administration |
E696662
|
entity |
| Predicate | fiscalBasis |
P91701
|
FINISHED |
| Object | land revenue |
—
|
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: land revenue | Statement: [Mughal administration, fiscalBasis, land revenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fiscalBasis Context triple: [Mughal administration, fiscalBasis, land revenue]
-
A.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
B.
fiscalInstrument
chosen
Indicates a financial tool or mechanism used to manage, allocate, or influence monetary resources, obligations, or economic activity.
-
C.
fiscalDuties
Indicates responsibilities or obligations related to managing, reporting, or overseeing financial resources and monetary matters.
-
D.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
E.
obligationBasis
Indicates the foundational reason, source, or justification upon which an obligation is based.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6319367488190b9985cc99c625053 |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:28 p.m.