Triple
T36055455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagford Parish Council |
E1042930
|
entity |
| Predicate | triggerEventInPlot |
P146205
|
FINISHED |
| Object | by-election after Barry Fairbrother’s death |
—
|
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: by-election after Barry Fairbrother’s death | Statement: [Pagford Parish Council, triggerEventInPlot, by-election after Barry Fairbrother’s death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerEventInPlot Context triple: [Pagford Parish Council, triggerEventInPlot, by-election after Barry Fairbrother’s death]
-
A.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
B.
triggerEventLocation
Indicates the location where a triggering event occurs or is initiated.
-
C.
triggerMethod
Indicates the method, mechanism, or procedure by which a particular event, action, or process is initiated or triggered.
-
D.
fireEvent
Indicates triggering or initiating a specific event or action within a system or process.
-
E.
connectedToPlotElement
chosen
Indicates that one element is linked or related to a specific plot element within a narrative structure.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.