Triple
T13474143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagford |
E318205
|
entity |
| Predicate | plotCatalystLocation |
P95150
|
FINISHED |
| Object | by-election for the Pagford Parish Council seat |
—
|
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 for the Pagford Parish Council seat | Statement: [Pagford, plotCatalystLocation, by-election for the Pagford Parish Council seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotCatalystLocation Context triple: [Pagford, plotCatalystLocation, by-election for the Pagford Parish Council seat]
-
A.
plotLocation
chosen
Indicates the relationship between a creative work and the place or setting where its story or events occur.
-
B.
plotElement
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
-
C.
locationOfDraw
Indicates that a draw or tie in a competition or game occurred at a particular location.
-
D.
showLocation
Indicates that one entity displays or reveals the position or place of another entity.
-
E.
designLocation
Indicates the place or setting where something is conceived, planned, or designed.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2447bc81908baf1f4b55095144 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.