Triple
T17735193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mudhoji Bhonsle |
E442694
|
entity |
| Predicate | goalOfPolicies |
P4658
|
FINISHED |
| Object | consolidation of Bhonsle authority |
—
|
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: consolidation of Bhonsle authority | Statement: [Mudhoji Bhonsle, goalOfPolicies, consolidation of Bhonsle authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfPolicies Context triple: [Mudhoji Bhonsle, goalOfPolicies, consolidation of Bhonsle authority]
-
A.
policyAim
Indicates that a policy is intended to achieve, promote, or be directed toward a particular goal or objective.
-
B.
nationalGoals
Indicates a relationship where certain objectives or targets are officially set or recognized as the goals of a nation.
-
C.
hasPolicyGoal
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
D.
politicalGoal
chosen
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
-
E.
supportsPolicyGoal
Indicates that one entity’s actions, positions, or characteristics help advance, uphold, or contribute to achieving a specified policy 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478eaff6c81909c7bd438b8c6c987 |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.