Triple
T7569916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monetary policy of India |
E179212
|
entity |
| Predicate | MPCVotingRule |
P2726
|
FINISHED |
| Object | each member has one vote |
—
|
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: each member has one vote | Statement: [Monetary policy of India, MPCVotingRule, each member has one vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MPCVotingRule Context triple: [Monetary policy of India, MPCVotingRule, each member has one vote]
-
A.
votingMethod
chosen
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
B.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
C.
majorityVote
Indicates that a decision or outcome is determined by the option receiving more than half of the votes among a group.
-
D.
votingSystemCouncil
Indicates a relationship where a council is responsible for establishing, overseeing, or making decisions about a voting system.
-
E.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f91ec780819099de6227a27bf5a5 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.