Triple
T30496006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HPG |
E776007
|
entity |
| Predicate | hasCommandersFrom |
P203308
|
FINISHED |
| Object | Kurdish population |
—
|
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: Kurdish population | Statement: [HPG, hasCommandersFrom, Kurdish population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommandersFrom Context triple: [HPG, hasCommandersFrom, Kurdish population]
-
A.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
C.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
D.
commandersInvolved
Indicates that specific commanders participated in, oversaw, or were directly involved in a particular event, operation, or engagement.
-
E.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
- F. None of above. chosen
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01531add1c8190b51add7bb046e2cb |
completed | May 11, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_6a014fef3d8c81909b509d51d0c4cdc7 |
completed | May 11, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_6a01531a3a4c8190ac8cb040cc36e96b |
completed | May 11, 2026, 3:55 a.m. |
Created at: April 29, 2026, 8:14 p.m.