Triple
T31904828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prorogation of Parliament (September 2019) |
E814518
|
entity |
| Predicate | affectedHouse |
P30038
|
FINISHED |
| Object | House of Commons |
—
|
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: House of Commons | Statement: [Prorogation of Parliament (September 2019), affectedHouse, House of Commons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedHouse Context triple: [Prorogation of Parliament (September 2019), affectedHouse, House of Commons]
-
A.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
B.
victimHouse
Indicates that a particular house is the residence or location associated with the victim in an incident or event.
-
C.
houseInvolved
chosen
Indicates that a house plays a significant role or is directly implicated in the specified event, situation, or relationship.
-
D.
affectedLand
Indicates that a piece of land is impacted or influenced by a particular event, action, or condition.
-
E.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, midnight