Triple
T33023722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non‑aldermanic Sheriff |
E844979
|
entity |
| Predicate | electionEvent |
P192051
|
FINISHED |
| Object | Midsummer Common Hall |
—
|
NE NERFINISHED |
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: Midsummer Common Hall | Statement: [Non‑aldermanic Sheriff, electionEvent, Midsummer Common Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionEvent Context triple: [Non‑aldermanic Sheriff, electionEvent, Midsummer Common Hall]
-
A.
electoralEventFor
chosen
Indicates that an electoral event (such as an election or referendum) is held for or associated with a specific political body, position, or jurisdiction.
-
B.
electionIs
Indicates that a particular event, process, or state qualifies as or constitutes an election.
-
C.
electionLeadingToEvent
Indicates that an election results in, triggers, or directly leads to a subsequent event.
-
D.
typeOfElectoralEvent
Indicates the specific kind or category of an electoral event that a given event instance belongs to.
-
E.
preElectionEvent
Indicates an event or activity that occurs in the period leading up to an election, typically related to campaigning, preparation, or election-related processes.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 1, 2026, 1:23 a.m.