Triple
T18142648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penal Laws in Ireland |
E434300
|
entity |
| Predicate | benefitedGroup |
P108329
|
FINISHED |
| Object | Anglican establishment |
—
|
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: Anglican establishment | Statement: [Penal Laws in Ireland, benefitedGroup, Anglican establishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitedGroup Context triple: [Penal Laws in Ireland, benefitedGroup, Anglican establishment]
-
A.
socialGroupBenefited
chosen
Indicates that a particular social group gains an advantage, improvement, or positive impact as a result of an action, event, or resource.
-
B.
beneficialMembers
Indicates that certain members of a group have a positive or advantageous effect on the group or on other entities.
-
C.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
D.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
-
E.
eligibleBeneficiaries
Indicates that certain parties meet the required conditions to receive benefits or entitlements under a given rule or program.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0c8aa88190b4ded7e6d05f6edf |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.