Triple
T11677323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durrani–Maratha War |
E277525
|
entity |
| Predicate | alliedWithMarathaSide |
P16682
|
FINISHED |
| Object | some Jat and Rajput chiefs |
—
|
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: some Jat and Rajput chiefs | Statement: [Durrani–Maratha War, alliedWithMarathaSide, some Jat and Rajput chiefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedWithMarathaSide Context triple: [Durrani–Maratha War, alliedWithMarathaSide, some Jat and Rajput chiefs]
-
A.
strength_Maratha_side
Indicates the level or extent of military or combat power associated with the Maratha side in a conflict or comparison.
-
B.
sideInBattleOfBuxar
Indicates being a participating side or party in the Battle of Buxar.
-
C.
laterFoughtAlongside
Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
-
D.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
E.
alliesInWar
chosen
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a46000a48190888ad1a6ade052e3 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.