Triple
T2541157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Battle of Panipat |
E56385
|
entity |
| Predicate | foughtBetween |
P12
|
FINISHED |
| Object | Maratha Empire and Durrani Empire |
—
|
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: Maratha Empire and Durrani Empire | Statement: [Third Battle of Panipat, foughtBetween, Maratha Empire and Durrani Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtBetween Context triple: [Third Battle of Panipat, foughtBetween, Maratha Empire and Durrani Empire]
-
A.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
B.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
C.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
D.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
E.
militaryConflict
chosen
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd64a2194819097c66cbeb37fe859 |
completed | March 7, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69abd0c4a5dc819097812db50443420a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.