Triple
T20321546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YPG |
E492216
|
entity |
| Predicate | designationByTurkey |
P87474
|
FINISHED |
| Object | terrorist organization |
—
|
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: terrorist organization | Statement: [YPG, designationByTurkey, terrorist organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationByTurkey Context triple: [YPG, designationByTurkey, terrorist organization]
-
A.
statusInTurkey
Indicates the legal, social, or official condition or standing that an entity holds within the context of Turkey.
-
B.
nameInTurkish
Indicates that an entity is known or referred to by a specific name in the Turkish language.
-
C.
affectedTurkishProvince
Indicates that a Turkish province is impacted or influenced by a specified event, condition, or entity.
-
D.
hasPopulationRankInTurkey
Indicates the relative position of an entity in the ordered list of populations within Turkey, such as its rank by population size compared to other entities in the country.
-
E.
legalRationaleClaimedByTurkey
chosen
Indicates that a particular legal rationale is asserted or invoked by Turkey as the basis for its position or actions.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.