Triple
T14156955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper House Hall |
E350836
|
entity |
| Predicate | statusOfUpperHouse |
P84036
|
FINISHED |
| Object | dissolved |
—
|
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: dissolved | Statement: [Upper House Hall, statusOfUpperHouse, dissolved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfUpperHouse Context triple: [Upper House Hall, statusOfUpperHouse, dissolved]
-
A.
upperHouseStatus
chosen
Indicates the status or role an entity holds within an upper legislative chamber (such as membership, position, or standing).
-
B.
stateHouseStatus
Indicates the current condition, operational state, or functional status of a state-level legislative house.
-
C.
upperHouseInvolved
Indicates that the upper legislative chamber (e.g., senate) participates in, influences, or is formally involved in the referenced action, process, or decision.
-
D.
upperHouse
Indicates that one entity functions as the higher or upper legislative chamber in relation to a given political or governmental system.
-
E.
upperHouseCounterpart
Indicates that one legislative body is the corresponding or equivalent chamber in the upper house relative to another body.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6135744c81909a43d659f5fe2895 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:58 a.m.