Triple
T11553703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryotwari system |
E273958
|
entity |
| Predicate | revenueRateBasis |
P6447
|
FINISHED |
| Object | estimated produce of land |
—
|
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: estimated produce of land | Statement: [Ryotwari system, revenueRateBasis, estimated produce of land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueRateBasis Context triple: [Ryotwari system, revenueRateBasis, estimated produce of land]
-
A.
fareBasis
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
-
B.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
C.
calculationBasis
chosen
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
D.
baseRate
Indicates the fundamental or standard rate at which something occurs or is charged, serving as a baseline before adjustments or modifiers are applied.
-
E.
revenueLevel
Indicates the relative amount or tier of revenue associated with an entity or activity.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a85b9ac8190a57c1fdaeacbe3d6 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.