Triple
T7870500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junbish-e Milli-ye Islami-ye Afghanistan |
E182723
|
entity |
| Predicate | armedForcesComposition |
P4889
|
FINISHED |
| Object | Uzbek fighters |
—
|
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: Uzbek fighters | Statement: [Junbish-e Milli-ye Islami-ye Afghanistan, armedForcesComposition, Uzbek fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForcesComposition Context triple: [Junbish-e Milli-ye Islami-ye Afghanistan, armedForcesComposition, Uzbek fighters]
-
A.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
B.
armedForcesInvolved
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
C.
militaryOrganization
chosen
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
D.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
-
E.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
- 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.