Triple
T7870493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junbish-e Milli-ye Islami-ye Afghanistan |
E182723
|
entity |
| Predicate | armedWingStatus |
P25765
|
FINISHED |
| Object | demobilized in part after 2001 |
—
|
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: demobilized in part after 2001 | Statement: [Junbish-e Milli-ye Islami-ye Afghanistan, armedWingStatus, demobilized in part after 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedWingStatus Context triple: [Junbish-e Milli-ye Islami-ye Afghanistan, armedWingStatus, demobilized in part after 2001]
-
A.
hasArmedWing
chosen
Indicates that an entity maintains, controls, or is associated with an organized armed or military wing.
-
B.
armamentStatus
Indicates the current condition or readiness level of an entity’s weapons or military equipment.
-
C.
hasWingConfiguration
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
D.
airWingType
Indicates the classification or category of an air wing associated with an entity.
-
E.
youthWingStatus
Indicates the status or role an entity holds within a youth wing organization, such as membership, affiliation, or position.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb384a285881908a5b2de278f9556f |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:55 p.m.