Triple
T30603534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quwwāt Sūriyā al-Dīmuqrāṭīya |
E778974
|
entity |
| Predicate | hasMainKurdishComponent |
P169606
|
FINISHED |
| Object | Yekîneyên Parastina Gel |
—
|
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: Yekîneyên Parastina Gel | Statement: [Quwwāt Sūriyā al-Dīmuqrāṭīya, hasMainKurdishComponent, Yekîneyên Parastina Gel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainKurdishComponent Context triple: [Quwwāt Sūriyā al-Dīmuqrāṭīya, hasMainKurdishComponent, Yekîneyên Parastina Gel]
-
A.
isKurdishLed
chosen
Indicates that an entity is primarily directed, governed, or dominated by Kurdish individuals or groups.
-
B.
hasArabComponent
Indicates that something includes or contains an Arab-related part, element, or component as one of its constituents.
-
C.
nameInKurdish
Indicates that an entity is referred to by a particular name in the Kurdish language.
-
D.
usesKunya
Indicates that one entity refers to or identifies another entity by a kunya (a teknonymic nickname, typically based on "father/mother of" someone).
-
E.
hasMainLocale
Indicates that an entity’s primary or default locale (language and regional setting) is a specified locale.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: April 29, 2026, 8:25 p.m.