Triple
T23782350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Basantar |
E587849
|
entity |
| Predicate | commanderPakistan |
P153915
|
FINISHED |
| Object | Lt Gen Irshad Hassan Khan |
—
|
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: Lt Gen Irshad Hassan Khan | Statement: [Battle of Basantar, commanderPakistan, Lt Gen Irshad Hassan Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderPakistan Context triple: [Battle of Basantar, commanderPakistan, Lt Gen Irshad Hassan Khan]
-
A.
governingAuthorityPakistaniSide
Indicates that an entity serves as the governing authority or administrative body on the Pakistani side of a border, region, or bilateral context.
-
B.
AfghanCommander
Indicates that an entity serves in the role of a military commander associated with Afghanistan.
-
C.
Muhammad Zia-ul-HaqTermEnd
Indicates the date or point in time when Muhammad Zia-ul-Haq’s term in office or official tenure ended.
-
D.
Ayub KhanTermEnd
Indicates the date or point in time when Ayub Khan’s term in office or position of authority concluded.
-
E.
Ayub KhanTermStart
Indicates the date or time when Ayub Khan began his term in a particular office or position.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62d7c608190b5fd0cf35f5faf42 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:16 p.m.