Triple
T26694101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich der Weise |
E672970
|
entity |
| Predicate | wasOffered |
P22295
|
FINISHED |
| Object | candidacy for Holy Roman Emperor in 1519 |
—
|
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: candidacy for Holy Roman Emperor in 1519 | Statement: [Friedrich der Weise, wasOffered, candidacy for Holy Roman Emperor in 1519]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOffered Context triple: [Friedrich der Weise, wasOffered, candidacy for Holy Roman Emperor in 1519]
-
A.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
B.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
C.
offering
chosen
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
D.
mayBeOfferedFor
Indicates that one entity can potentially be provided or made available as an option to another entity.
-
E.
offeringOutcome
Indicates the result or consequence that follows from making a particular offering.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6177ab31c8190ad205a5fed1ec9d8 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:27 a.m.