Triple
T34959441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man Singh I of Amber |
E1008211
|
entity |
| Predicate | opponentInBattleOfHaldighati |
P182135
|
FINISHED |
| Object | Maharana Pratap |
—
|
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: Maharana Pratap | Statement: [Man Singh I of Amber, opponentInBattleOfHaldighati, Maharana Pratap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInBattleOfHaldighati Context triple: [Man Singh I of Amber, opponentInBattleOfHaldighati, Maharana Pratap]
-
A.
sideInBattleOfBuxar
Indicates being a participating side or party in the Battle of Buxar.
-
B.
combatantRulerMughals
Indicates a ruler associated with the Mughal Empire who participated as a combatant in a specific conflict or battle.
-
C.
opponentAtSekigahara
Indicates that two entities were opposing sides against each other in the Battle of Sekigahara.
-
D.
successorAsMughalAlly
Indicates that one entity becomes the next political or military ally of the Mughal power, taking over that allied role from another entity.
-
E.
primaryAdversaryOfMysore
Indicates that one entity served as the main or most significant opponent or enemy of Mysore.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7870dfe108190996c0c68630edc7f |
completed | May 3, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4 p.m.