Triple
T37709059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jijamata |
E939275
|
entity |
| Predicate | roleInShivajiLife |
P100864
|
FINISHED |
| Object | primary moral and spiritual guide |
—
|
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: primary moral and spiritual guide | Statement: [Jijamata, roleInShivajiLife, primary moral and spiritual guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInShivajiLife Context triple: [Jijamata, roleInShivajiLife, primary moral and spiritual guide]
-
A.
roleInShivajisLife
chosen
Indicates the specific role, influence, or significance an entity had in the life of Shivaji.
-
B.
roleInAkbarsLife
Indicates the specific role, position, or significance that one entity held in relation to Akbar’s life.
-
C.
roleInHistoryOf
Indicates that one entity holds a specific role, contribution, or significance within the historical development or narrative of another entity.
-
D.
roleAtPanipat
Indicates the specific role, position, or function an entity held in relation to the Battle of Panipat.
-
E.
roleInCarnaticWars
Indicates the role or involvement an entity had in the events of the Carnatic Wars.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02fc3890a881908b69b0f2d7cc1ce1 |
completed | May 12, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_6a02fb98438c8190938896c00216b9ec |
completed | May 12, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:18 p.m.