Triple
T9119892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father of the House of Lords |
E218817
|
entity |
| Predicate | triggerForChange |
P29885
|
FINISHED |
| Object | death of incumbent |
—
|
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: death of incumbent | Statement: [Father of the House of Lords, triggerForChange, death of incumbent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerForChange Context triple: [Father of the House of Lords, triggerForChange, death of incumbent]
-
A.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
B.
triggerCondition
chosen
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
C.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
D.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
-
E.
functionChange
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a902e08190a7eb4728f32b9e1d |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.