Triple
T9423471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hereditary Chamber of Peers |
E227211
|
entity |
| Predicate | chamberRole |
P88796
|
FINISHED |
| Object | review of legislation |
—
|
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: review of legislation | Statement: [hereditary Chamber of Peers, chamberRole, review of legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberRole Context triple: [hereditary Chamber of Peers, chamberRole, review of legislation]
-
A.
namedForChamber
Indicates that one entity is named after, or in honor of, a particular chamber (such as a legislative or deliberative body).
-
B.
forChamber
Indicates that something is intended for use in, associated with, or belonging to a particular chamber.
-
C.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
D.
isChamber
Indicates that one entity functions as a chamber, room, or enclosed space in relation to another entity.
-
E.
chamberOf
Indicates that one entity is a chamber, room, or enclosed space that is part of, contained within, or assigned to another entity.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c29b4348190b45103e9ebd82aa4 |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:48 p.m.