Triple
T11553693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryotwari system |
E273958
|
entity |
| Predicate | landRevenuePaidBy |
P100100
|
FINISHED |
| Object | ryot |
—
|
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: ryot | Statement: [Ryotwari system, landRevenuePaidBy, ryot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landRevenuePaidBy Context triple: [Ryotwari system, landRevenuePaidBy, ryot]
-
A.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
B.
taxCollectorFor
Indicates that one entity is responsible for collecting taxes on behalf of another entity, such as a government, organization, or jurisdiction.
-
C.
revenueSources
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
D.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
-
E.
taxPoint
Indicates the specific time or event at which a tax obligation is considered to arise or become chargeable for a transaction or 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_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. |
| PDg | Predicate description generation | batch_69d822f00a088190ac6b48e45e743899 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.