Triple
T26490737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutory Instruments of Ireland |
E669148
|
entity |
| Predicate | canBeAnnulledBy |
P40058
|
FINISHED |
| Object | Oireachtas |
—
|
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: Oireachtas | Statement: [Statutory Instruments of Ireland, canBeAnnulledBy, Oireachtas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAnnulledBy Context triple: [Statutory Instruments of Ireland, canBeAnnulledBy, Oireachtas]
-
A.
annulledBy
chosen
Indicates that an action, decision, or agreement has been officially invalidated or rendered void by a specified authority or agent.
-
B.
canBeAbolishedBy
Indicates that one entity has the authority or power to formally end, revoke, or eliminate another entity.
-
C.
canBeCancelled
Indicates that an action, event, or agreement is eligible to be terminated or revoked before completion.
-
D.
canRepeal
Indicates that one entity has the authority or power to revoke, annul, or cancel a rule, decision, or action established by another entity.
-
E.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 1:03 a.m.