Triple
T828230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Minister’s Questions |
E17903
|
entity |
| Predicate | significantChange |
P13888
|
FINISHED |
| Object | moved to a single weekly session in 1997 |
—
|
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: moved to a single weekly session in 1997 | Statement: [Prime Minister’s Questions, significantChange, moved to a single weekly session in 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantChange Context triple: [Prime Minister’s Questions, significantChange, moved to a single weekly session in 1997]
-
A.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
-
B.
notableChange
chosen
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
E.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab99b1e48190afad1f073348b29a |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.