Triple
T36828775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sholinghur |
E910079
|
entity |
| Predicate | notableCommanderForMysore |
P17957
|
FINISHED |
| Object | Hyder Ali |
E255275
|
NE 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: Hyder Ali | Statement: [Battle of Sholinghur, notableCommanderForMysore, Hyder Ali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderForMysore Context triple: [Battle of Sholinghur, notableCommanderForMysore, Hyder Ali]
-
A.
landCommanderMysore
Indicates that an entity serves as the land forces commander for Mysore.
-
B.
primaryAdversaryOfMysore
Indicates that one entity served as the main or most significant opponent or enemy of Mysore.
-
C.
notableCommanderOf
chosen
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
D.
notableCommanderUnder
Indicates that one entity served as a notable military commander under the authority or leadership of another entity.
-
E.
notableCommanderInBurmaOperations
Indicates that the subject served as a prominent or distinguished military commander in operations conducted in Burma.
- F. None of above.
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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e57489a1c819087894d8730aefa22 |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.