Triple
T30495985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HPG |
E776007
|
entity |
| Predicate | commandStructureOf |
P6017
|
FINISHED |
| Object | PKK armed 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: PKK armed forces | Statement: [HPG, commandStructureOf, PKK armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandStructureOf Context triple: [HPG, commandStructureOf, PKK armed forces]
-
A.
commandStructureUnion
Indicates a relationship where multiple command structures are combined or unified into a single coordinated command framework.
-
B.
commandStructureEnglish
Indicates that one entity holds a position or role within the command hierarchy or organizational structure of another entity in an English-language context.
-
C.
commandStructureInfluencedBy
Indicates that the organization or hierarchy of authority within a command structure is shaped, guided, or altered by another entity or factor.
-
D.
hasCommandStructure
chosen
Indicates that one entity possesses an organized hierarchy of authority or control that governs another entity or set of entities.
-
E.
commandSyntax
Indicates the specific structure or format in which a command must be written or expressed.
- 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_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:14 p.m.