Triple
T30496107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koma Civakên Kurdistan |
E776009
|
entity |
| Predicate | hasIdeologicalCore |
P16870
|
FINISHED |
| Object | Öcalanism |
—
|
NE NERFINISHED |
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: Öcalanism | Statement: [Koma Civakên Kurdistan, hasIdeologicalCore, Öcalanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdeologicalCore Context triple: [Koma Civakên Kurdistan, hasIdeologicalCore, Öcalanism]
-
A.
ideologicalCore
chosen
Indicates that one entity represents the central or foundational set of beliefs, values, or principles that fundamentally shape and guide another entity’s ideology.
-
B.
hasIdeologicalOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a particular ideology.
-
C.
hasIdeologicalRole
Indicates that an entity holds or fulfills a specific function, position, or influence within an ideology or ideological framework.
-
D.
hasIdeologicalPosition
Indicates that an entity holds, endorses, or is associated with a particular ideological stance or viewpoint.
-
E.
hasIdeologicalConflict
Indicates a relationship where two entities hold opposing or incompatible ideologies that put them in conflict with each other.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6877beac8819088e18617985213a8 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:14 p.m.