Triple
T11553723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryotwari system |
E273958
|
entity |
| Predicate | goalClaimedByOfficials |
P72497
|
FINISHED |
| Object | protect peasant proprietors |
—
|
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: protect peasant proprietors | Statement: [Ryotwari system, goalClaimedByOfficials, protect peasant proprietors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalClaimedByOfficials Context triple: [Ryotwari system, goalClaimedByOfficials, protect peasant proprietors]
-
A.
courtOfficial
Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
-
B.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
C.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
D.
officialGoal
chosen
Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
-
E.
clinchingGoalControversy
Indicates a dispute or debate over the legitimacy or correctness of a decisive, game-winning goal.
- 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.