Triple
T13806640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Council of the Slovak Republic |
E331776
|
entity |
| Predicate | hasDeputyHeads |
P111544
|
FINISHED |
| Object | Deputy Speakers |
—
|
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: Deputy Speakers | Statement: [National Council of the Slovak Republic, hasDeputyHeads, Deputy Speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeputyHeads Context triple: [National Council of the Slovak Republic, hasDeputyHeads, Deputy Speakers]
-
A.
hasNumberOfDeputies
Indicates the specific count of deputies associated with or assigned to an entity.
-
B.
hasDeputyLeaderTitle
Indicates that an entity holds a specific title associated with the role of deputy leader.
-
C.
hasDeputyChiefMinister
Indicates that an entity serves as the deputy chief minister of another entity (typically a political jurisdiction or government).
-
D.
mayHaveDeputy
Indicates that an entity is allowed or entitled to have another entity serving as its deputy or subordinate representative.
-
E.
hasDeputeLeader
Indicates that an entity serves as the deputy leader (second-in-command) of another entity.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026d98108190acf366a36d97bf92 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:12 p.m.