Triple
T993919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick the Wise |
E21451
|
entity |
| Predicate | votedFor |
P5054
|
FINISHED |
| Object | election of Charles V as Holy Roman Emperor |
—
|
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: election of Charles V as Holy Roman Emperor | Statement: [Frederick the Wise, votedFor, election of Charles V as Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votedFor Context triple: [Frederick the Wise, votedFor, election of Charles V as Holy Roman Emperor]
-
A.
voteFor
chosen
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
C.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
D.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
E.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4c5e16881908cd5f7ba2fcd5084 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2af071c819086c374a16307dfe0 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.