Triple
T3490039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-elector of Mainz |
E73704
|
entity |
| Predicate | numberOfVotesInImperialElection |
P48694
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Prince-elector of Mainz, numberOfVotesInImperialElection, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVotesInImperialElection Context triple: [Prince-elector of Mainz, numberOfVotesInImperialElection, 1]
-
A.
electoratesCalled
Indicates that specific electoral districts or constituencies are given particular names or designations.
-
B.
numberOfBallots
Indicates the total count of ballots associated with a particular election, contest, or voting event.
-
C.
electoralVoteFor
Indicates that a specified number of electoral votes are allocated or cast in favor of a particular candidate or option in an election.
-
D.
numberOfSeatsWon
Indicates the quantity of seats secured by an entity (such as a party or candidate) in an election or representative body.
-
E.
electoralVotesReceived
Indicates that one entity received a specified number of electoral votes in an election from another entity or jurisdiction.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb94190c8190a81eb41042e51a00 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb055ed2481908171effe28151cf9 |
completed | March 8, 2026, 5:22 p.m. |
Created at: March 8, 2026, 3:18 p.m.