Triple
T936224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Ireland |
E20199
|
entity |
| Predicate | houseOfLordsMembershipBasis |
P14822
|
FINISHED |
| Object | hereditary peers |
—
|
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: hereditary peers | Statement: [Parliament of Ireland, houseOfLordsMembershipBasis, hereditary peers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseOfLordsMembershipBasis Context triple: [Parliament of Ireland, houseOfLordsMembershipBasis, hereditary peers]
-
A.
houseMembership
Indicates that an entity belongs to, or is a member of, a particular house or household.
-
B.
positionInHouseOfLords
Indicates that an entity holds or held a specific official role or title within the House of Lords.
-
C.
relationshipToHouseOfCommons
Indicates the nature or type of connection an entity has to the House of Commons, such as membership, representation, or institutional association.
-
D.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
-
E.
houseRepresentationBasis
chosen
Indicates the foundational criteria or rationale on which a particular representation of a house is based.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b36558588190a2a9c710073624d1 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.