Triple
T15924391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adem Jashari |
E386169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kosovo Liberation Army commander |
C3668
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Kosovo Liberation Army commander Context triple: [Adem Jashari, instanceOf, Kosovo Liberation Army commander]
-
A.
Chetnik leader
A Chetnik leader is a commanding figure within the Chetnik movement, responsible for organizing, directing, and representing its military and political activities.
-
B.
Yugoslav military officer
A Yugoslav military officer is a commissioned member of the armed forces of the former Socialist Federal Republic of Yugoslavia, responsible for leading troops, planning and executing military operations, and upholding the doctrines and political-military objectives of the Yugoslav state.
-
C.
guerrilla leader
chosen
A guerrilla leader is a commander who organizes, directs, and motivates small, irregular combat groups to conduct unconventional warfare, often using hit-and-run tactics and local support against a typically stronger adversary.
-
D.
Serbian general
A Serbian general is a high-ranking military officer from Serbia responsible for leading and commanding large military formations, planning operations, and shaping national defense strategy.
-
E.
Kurdish leader
A Kurdish leader is an individual who holds a position of political, social, or military authority within Kurdish communities, guiding collective goals such as self-determination, cultural preservation, and regional governance.
- F. None of above.
Provenance (1 batch)
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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.