Triple
T30496108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koma Civakên Kurdistan |
E776009
|
entity |
| Predicate | claimsToReject |
P180051
|
FINISHED |
| Object | nation-state model |
—
|
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: nation-state model | Statement: [Koma Civakên Kurdistan, claimsToReject, nation-state model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsToReject Context triple: [Koma Civakên Kurdistan, claimsToReject, nation-state model]
-
A.
claimsToEliminate
Indicates that one entity asserts it will remove, eradicate, or put an end to another entity or condition.
-
B.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
C.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
rejectedClaim
Indicates that one party has refused to accept, approve, or validate a claim made by another party.
-
E.
claimsToSeparate
Indicates that one entity asserts or promises that it will divide, detach, or distinguish one thing from another.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 29, 2026, 8:14 p.m.