Triple
T30495955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teyrêbazên Azadîya Kurdistanê |
E776006
|
entity |
| Predicate | relationshipWithPKK |
P86765
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [Teyrêbazên Azadîya Kurdistanê, relationshipWithPKK, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithPKK Context triple: [Teyrêbazên Azadîya Kurdistanê, relationshipWithPKK, disputed]
-
A.
relationshipToPKK
chosen
Indicates the nature or type of connection an entity has with the PKK (Kurdistan Workers' Party), such as affiliation, support, opposition, or other defined relationship.
-
B.
positionOnPKK
Indicates a stance, opinion, or policy that an entity holds regarding the PKK.
-
C.
relationshipToAllPalestineGovernment
Indicates the nature or type of relationship an entity has with the All-Palestine Government.
-
D.
relationshipWithOtherGroup
Indicates that one group has some defined connection, association, or interaction with another distinct group.
-
E.
relationshipToPula
Indicates the type or nature of a relationship that an entity has with Pula.
- 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_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
Created at: April 29, 2026, 8:14 p.m.