Triple
T38695040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimbalkar family |
E949973
|
entity |
| Predicate | roleInMarathaHistory |
P100864
|
FINISHED |
| Object | early supporters and allies of Shivaji |
—
|
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: early supporters and allies of Shivaji | Statement: [Nimbalkar family, roleInMarathaHistory, early supporters and allies of Shivaji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMarathaHistory Context triple: [Nimbalkar family, roleInMarathaHistory, early supporters and allies of Shivaji]
-
A.
roleInBattleOfHaldighati
Indicates the specific role or involvement an entity had in the Battle of Haldighati.
-
B.
roleInShivajisLife
chosen
Indicates the specific role, influence, or significance an entity had in the life of Shivaji.
-
C.
roleAtPanipat
Indicates the specific role, position, or function an entity held in relation to the Battle of Panipat.
-
D.
roleInBattleOfPlassey
Indicates the specific role or involvement an entity had in the Battle of Plassey.
-
E.
roleInHistoryOf
Indicates that one entity holds a specific role, contribution, or significance within the historical development or narrative of another entity.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:33 p.m.