Triple
T38125272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maratha military leadership at Panipat |
E952049
|
entity |
| Predicate | cavalryCommander |
P68449
|
FINISHED |
| Object | Malhar Rao Holkar |
—
|
NE NERFINISHED |
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: Malhar Rao Holkar | Statement: [Maratha military leadership at Panipat, cavalryCommander, Malhar Rao Holkar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cavalryCommander Context triple: [Maratha military leadership at Panipat, cavalryCommander, Malhar Rao Holkar]
-
A.
hasCavalryRole
Indicates that an entity serves in, is assigned to, or performs duties associated with a cavalry role.
-
B.
UnionCavalryCommander
Indicates that the subject serves as a commander of cavalry forces for the Union side in a conflict.
-
C.
capturedCommander
Indicates that one party has taken a military commander from another party into custody or control.
-
D.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
E.
sideCommander
chosen
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.