Triple
T38282054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Unit |
E1022103
|
entity |
| Predicate | functionWithinTaliban |
P119470
|
FINISHED |
| Object | serves as a strategic reserve force |
—
|
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: serves as a strategic reserve force | Statement: [Red Unit, functionWithinTaliban, serves as a strategic reserve force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionWithinTaliban Context triple: [Red Unit, functionWithinTaliban, serves as a strategic reserve force]
-
A.
positionInTaliban
chosen
Indicates that an individual holds or has held an official role, rank, or function within the Taliban organization.
-
B.
statusInAfghanistan
Indicates the condition, role, or legal standing an entity holds within the context of Afghanistan.
-
C.
positionOnTerrorism
Indicates a stance or viewpoint that an entity holds regarding terrorism, such as its causes, legitimacy, or appropriate responses.
-
D.
successorAsTalibanLeader
Indicates that one individual became the next leader of the Taliban after another individual.
-
E.
unitInvolvedPakistan
Indicates that a unit is involved in or associated with activities, operations, or events in Pakistan.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.