Triple
T26694196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial election of 1519 |
E672972
|
entity |
| Predicate | elector |
P180846
|
FINISHED |
| Object | Elector of Mainz |
—
|
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: Elector of Mainz | Statement: [Imperial election of 1519, elector, Elector of Mainz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elector Context triple: [Imperial election of 1519, elector, Elector of Mainz]
-
A.
electorCollege
Indicates that an entity serves as a member of an electoral college responsible for formally selecting or voting for another entity, typically in a political or organizational election.
-
B.
partyOfElector
Indicates the political party with which a given elector is affiliated or on whose behalf the elector acts.
-
C.
electedCandidate
Indicates that a particular person has been chosen as the winner in an election for a given position or office.
-
D.
electoralFront
Indicates a political alliance or coalition formed by multiple parties or groups to contest elections together as a unified front.
-
E.
electionWinner
Indicates that the subject is the candidate who received the highest support and officially won a particular election.
- F. None of above. chosen
Provenance (4 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 27, 2026, 3:27 a.m.