Triple
T31676333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 27th Parliament of Turkey |
E808408
|
entity |
| Predicate | hasFirstDeputySpeaker |
P120291
|
FINISHED |
| Object | Levent Gök |
—
|
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: Levent Gök | Statement: [27th Parliament of Turkey, hasFirstDeputySpeaker, Levent Gök]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstDeputySpeaker Context triple: [27th Parliament of Turkey, hasFirstDeputySpeaker, Levent Gök]
-
A.
hasDeputyChiefMinister
Indicates that an entity serves as the deputy chief minister of another entity (typically a political jurisdiction or government).
-
B.
hasDeputeLeader
Indicates that an entity serves as the deputy leader (second-in-command) of another entity.
-
C.
deputySpeaker
chosen
Indicates that one entity serves as the deputy or vice speaker (second-in-command presiding officer) in relation to a legislative or deliberative body.
-
D.
hasDeputyHeads
Indicates that an entity has one or more individuals serving in subordinate leadership roles as deputy heads.
-
E.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 30, 2026, 11:03 p.m.