Triple
T34275056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig II. von Ungarn und Böhmen |
E879428
|
entity |
| Predicate | RegierungsantrittAlsKönigVonBöhmen |
P62199
|
FINISHED |
| Object | 1516 |
—
|
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: 1516 | Statement: [Ludwig II. von Ungarn und Böhmen, RegierungsantrittAlsKönigVonBöhmen, 1516]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RegierungsantrittAlsKönigVonBöhmen Context triple: [Ludwig II. von Ungarn und Böhmen, RegierungsantrittAlsKönigVonBöhmen, 1516]
-
A.
reignStartAsKingOfBohemia
chosen
Indicates the date or event marking when an individual began their reign as King of Bohemia.
-
B.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
-
C.
reignEndAsKingOfBohemia
Indicates the time or event at which an individual’s period of ruling as king of Bohemia comes to an end.
-
D.
predecessorAsKingOfBohemia
Indicates that one entity was the immediately preceding holder of the kingship of Bohemia relative to another entity.
-
E.
coronationPlaceAsKingOfBohemia
Indicates the place where an individual was ceremonially crowned as King of Bohemia.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:56 a.m.