Triple
T27573401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atta Muhammad Nur |
E696092
|
entity |
| Predicate | roleDuringTalibanRegime |
P108011
|
FINISHED |
| Object | Northern Alliance 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: Northern Alliance commander | Statement: [Atta Muhammad Nur, roleDuringTalibanRegime, Northern Alliance commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringTalibanRegime Context triple: [Atta Muhammad Nur, roleDuringTalibanRegime, Northern Alliance commander]
-
A.
positionInTaliban
Indicates that an individual holds or has held an official role, rank, or function within the Taliban organization.
-
B.
roleInPakistan
Indicates that an entity holds or has held a specific role, position, or function within the context of Pakistan.
-
C.
roleDuringSaddamRule
Indicates that an entity held a specific role, position, or function during the period of Saddam Hussein's rule.
-
D.
terroristRole
Indicates that an entity plays a specific functional role within a terrorist organization or terrorist activity.
-
E.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fee64148190b84b7a1b6e9cccbe |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:44 p.m.