Triple
T21584487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akron municipal elections |
E532612
|
entity |
| Predicate | hasElectoralOfficeLevel |
P119959
|
FINISHED |
| Object | local |
—
|
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: local | Statement: [Akron municipal elections, hasElectoralOfficeLevel, local]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectoralOfficeLevel Context triple: [Akron municipal elections, hasElectoralOfficeLevel, local]
-
A.
hasElectoralLevel
chosen
Indicates that one entity is associated with a specific tier or level within an electoral or voting system.
-
B.
isElectoralOffice
Indicates that the referenced position or role is an official public office filled through an electoral process.
-
C.
stateLevelOfficeHeld
Indicates that an entity has held a public office or position within a state-level government.
-
D.
hasBallotAccessForOffice
Indicates that an entity is legally permitted to appear on the election ballot as a candidate for a specified office.
-
E.
hasElectoralAuthority
Indicates that an entity possesses the official power or legal right to oversee, manage, or make binding decisions about electoral processes or outcomes.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5f2cc0819095552de70eb2ad8d |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.