Triple
T27063977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 31st Dáil |
E685122
|
entity |
| Predicate | hasDeputySpeakerRole |
P120291
|
FINISHED |
| Object | Leas-Cheann Comhairle |
—
|
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: Leas-Cheann Comhairle | Statement: [31st Dáil, hasDeputySpeakerRole, Leas-Cheann Comhairle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeputySpeakerRole Context triple: [31st Dáil, hasDeputySpeakerRole, Leas-Cheann Comhairle]
-
A.
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.
-
B.
hasDeputyChiefMinister
Indicates that an entity serves as the deputy chief minister of another entity (typically a political jurisdiction or government).
-
C.
hasDeputeLeader
Indicates that an entity serves as the deputy leader (second-in-command) of another entity.
-
D.
isSecondChamberSpeaker
Indicates that the subject holds the position of speaker/presiding officer of a legislature’s second chamber (e.g., upper or lower house, depending on the system).
-
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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 8:23 a.m.