Triple
T30496000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HPG |
E776007
|
entity |
| Predicate | claimsTargetFocus |
P31
|
FINISHED |
| Object | Turkish military and security forces |
—
|
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: Turkish military and security forces | Statement: [HPG, claimsTargetFocus, Turkish military and security forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsTargetFocus Context triple: [HPG, claimsTargetFocus, Turkish military and security forces]
-
A.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
B.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
-
C.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
E.
focusTrait
Indicates that one entity is characterized by, or primarily associated with, a particular trait or attribute of another entity.
- 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_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:14 p.m.