Triple
T34837414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mudki |
E1004237
|
entity |
| Predicate | primaryBritishCommanderRank |
P205577
|
FINISHED |
| Object | Commander-in-Chief, India |
E85084
|
NE 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: Commander-in-Chief, India | Statement: [Battle of Mudki, primaryBritishCommanderRank, Commander-in-Chief, India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBritishCommanderRank Context triple: [Battle of Mudki, primaryBritishCommanderRank, Commander-in-Chief, India]
-
A.
commandingOfficerRank
Indicates the military rank held by the officer who has command authority over a given individual or unit.
-
B.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
C.
initialCommanderRank
Indicates the military rank an individual held at the time they first assumed a commander position.
-
D.
governmentCommanderRank
Indicates that an individual holds a specific rank within a government’s command or leadership hierarchy.
-
E.
equivalentRankInBritishArmy
Indicates that two military positions are considered to have the same rank level within the structure of the British Army.
- F. None of above. chosen
Provenance (5 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fc50cf481908404d19dedf264ed |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4 p.m.