Triple
T37858388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forces of Hemu |
E944254
|
entity |
| Predicate | statusAfterSecondBattleOfPanipat |
P201399
|
FINISHED |
| Object | effectively destroyed |
—
|
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: effectively destroyed | Statement: [Forces of Hemu, statusAfterSecondBattleOfPanipat, effectively destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterSecondBattleOfPanipat Context triple: [Forces of Hemu, statusAfterSecondBattleOfPanipat, effectively destroyed]
-
A.
sideInBattleOfPanipat
Indicates participation as a particular side or faction in the Battle of Panipat.
-
B.
sideInBattleOfHaldighati
Indicates participation as a particular side or faction in the Battle of Haldighati.
-
C.
roleAtPanipat
Indicates the specific role, position, or function an entity held in relation to the Battle of Panipat.
-
D.
opponentInBattleOfHaldighati
Indicates that two entities stood on opposing sides as adversaries in the Battle of Haldighati.
-
E.
effectOnMarathas
Indicates the impact or consequences that something has on the Marathas.
- F. None of above. chosen
Provenance (4 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_69fff09ce63881908e7f91a3d35d969f |
completed | May 10, 2026, 2:42 a.m. |
Created at: May 3, 2026, 4:19 p.m.