Triple
T34448930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathaoirleach of Seanad Éireann |
E884306
|
entity |
| Predicate | canCallToOrder |
P178955
|
FINISHED |
| Object | members of Seanad Éireann |
—
|
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: members of Seanad Éireann | Statement: [Cathaoirleach of Seanad Éireann, canCallToOrder, members of Seanad Éireann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCallToOrder Context triple: [Cathaoirleach of Seanad Éireann, canCallToOrder, members of Seanad Éireann]
-
A.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
B.
canBeCalledTo
Indicates that one entity is able or permitted to initiate a call or summon another entity.
-
C.
canBeServed
Indicates that an entity is eligible or suitable to be provided, delivered, or made available for use or consumption.
-
D.
canBeCalledOutFor
Indicates that one entity is subject to being criticized, challenged, or held accountable by another for its actions, behavior, or statements.
-
E.
isOrderedTo
Indicates that one entity has been formally directed or commanded to perform an action or fulfill a duty by another authority.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.