Triple
T34275064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig II. von Ungarn und Böhmen |
E879428
|
entity |
| Predicate | RegierungszeitAlsKönigVonBöhmen |
P179642
|
FINISHED |
| Object | 1516–1526 |
—
|
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–1526 | Statement: [Ludwig II. von Ungarn und Böhmen, RegierungszeitAlsKönigVonBöhmen, 1516–1526]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RegierungszeitAlsKönigVonBöhmen Context triple: [Ludwig II. von Ungarn und Böhmen, RegierungszeitAlsKönigVonBöhmen, 1516–1526]
-
A.
reignEndAsKingOfBohemia
Indicates the time or event at which an individual’s period of ruling as king of Bohemia comes to an end.
-
B.
reignStartAsKingOfBohemia
Indicates the date or event marking when an individual began their reign as King of Bohemia.
-
C.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
-
D.
predecessorAsKingOfBohemia
Indicates that one entity was the immediately preceding holder of the kingship of Bohemia relative to another entity.
-
E.
reignAsQueenConsortOfBohemiaEnd
Indicates the time or event at which an individual’s tenure as queen consort of Bohemia comes to an end.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 1:56 a.m.