Triple
T24559923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Abbacy of Kempten |
E607622
|
entity |
| Predicate | heldVoteIn |
P156325
|
FINISHED |
| Object | Imperial Diet |
—
|
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: Imperial Diet | Statement: [Prince-Abbacy of Kempten, heldVoteIn, Imperial Diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldVoteIn Context triple: [Prince-Abbacy of Kempten, heldVoteIn, Imperial Diet]
-
A.
heldConfidenceVoteIn
Indicates that a confidence vote was conducted within a specified governing body, assembly, or context.
-
B.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
C.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
-
D.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
E.
heldElectoralVoteFor
Indicates that an elector or jurisdiction cast its official electoral vote in favor of a particular candidate in an 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f57a7c8190a0eb8d6d6ef6ae61 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.