Triple
T27142611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electoral (Amendment) Act 1995 |
E681853
|
entity |
| Predicate | parliamentAffected |
P27346
|
FINISHED |
| Object | Dáil Éireann |
—
|
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: Dáil Éireann | Statement: [Electoral (Amendment) Act 1995, parliamentAffected, Dáil Éireann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentAffected Context triple: [Electoral (Amendment) Act 1995, parliamentAffected, Dáil Éireann]
-
A.
effectOnParliament
Indicates the impact or influence that one action, event, or entity has on the functioning, decisions, or status of a parliament.
-
B.
containsParliament
Indicates that one political or administrative entity includes a parliament within its structure or jurisdiction.
-
C.
legislatureAffected
chosen
Indicates that an action, event, or measure has an impact on a legislative body or its functioning.
-
D.
parliamentaryInvolvement
Indicates involvement or participation of an entity in the activities, processes, or functions of a parliament or parliamentary body.
-
E.
usesParliament
Indicates that one entity conducts its legislative or decision‑making processes through a parliamentary body or system.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 9:10 a.m.