Triple
T7837972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ismail Khan |
E181732
|
entity |
| Predicate | roleDuringSovietAfghanWar |
P9463
|
FINISHED |
| Object | mujahideen field commander |
—
|
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: mujahideen field commander | Statement: [Ismail Khan, roleDuringSovietAfghanWar, mujahideen field commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringSovietAfghanWar Context triple: [Ismail Khan, roleDuringSovietAfghanWar, mujahideen field commander]
-
A.
roleDuringBlackHawkWar
Indicates the specific role, position, or function an entity held during the Black Hawk War.
-
B.
roleInSovietUnion
Indicates that an entity held a specific position, function, or status within the governmental, political, or institutional structure of the Soviet Union.
-
C.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
roleDuringColdWar
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
-
E.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
- 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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb14c336f08190a21a3fcaa7269457 |
completed | March 31, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cae91e98988190abd4ece75932c589 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:46 p.m.