Triple
T37853228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Salher |
E944111
|
entity |
| Predicate | opposingRuler |
P63201
|
FINISHED |
| Object | Aurangzeb |
—
|
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: Aurangzeb | Statement: [Battle of Salher, opposingRuler, Aurangzeb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingRuler Context triple: [Battle of Salher, opposingRuler, Aurangzeb]
-
A.
opposingMonarch
Indicates that two monarchs are in opposition to each other, typically as rivals, enemies, or leaders of conflicting factions or states.
-
B.
opponentMonarch
chosen
Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
-
C.
opposedRegent
Indicates that one party actively resisted, challenged, or worked against the authority or actions of a regent.
-
D.
traditionallyOpposedRuler
Indicates that one entity has historically or customarily been in opposition to the rule or authority of another entity.
-
E.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:19 p.m.