Triple
T5336392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardoli Satyagraha |
E123835
|
entity |
| Predicate | agreementOutcome |
P62908
|
FINISHED |
| Object | reduction of land revenue rates |
—
|
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: reduction of land revenue rates | Statement: [Bardoli Satyagraha, agreementOutcome, reduction of land revenue rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agreementOutcome Context triple: [Bardoli Satyagraha, agreementOutcome, reduction of land revenue rates]
-
A.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
B.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
C.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
D.
agreementInvoked
Indicates that a formal agreement or contract has been activated, called upon, or put into effect between the related entities.
-
E.
proposalOutcome
Indicates the result or status assigned to a proposal after it has been evaluated or decided upon.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85b104c081908b81236a0142e1c8 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.