Triple
T31409906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MHP |
E801230
|
entity |
| Predicate | positionOnPKK |
P196950
|
FINISHED |
| Object | strongly opposes PKK |
—
|
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: strongly opposes PKK | Statement: [MHP, positionOnPKK, strongly opposes PKK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnPKK Context triple: [MHP, positionOnPKK, strongly opposes PKK]
-
A.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionConfirmedBy
Indicates that the validity or accuracy of a position (e.g., spatial, organizational, or conceptual) is verified or endorsed by a specified confirming entity.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: April 30, 2026, 8:37 p.m.