Triple
T34275055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig II. von Ungarn und Böhmen |
E879428
|
entity |
| Predicate | RegierungsantrittAlsKönigVonUngarn |
P34897
|
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önigVonUngarn, 1516]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RegierungsantrittAlsKönigVonUngarn Context triple: [Ludwig II. von Ungarn und Böhmen, RegierungsantrittAlsKönigVonUngarn, 1516]
-
A.
reignAsKingOfHungaryStart
chosen
Indicates the time at which an individual begins their reign as king of Hungary.
-
B.
reignAsKingOfHungaryEnd
Indicates the time or event at which an entity’s reign as King of Hungary comes to an end.
-
C.
successorAsKingOfHungary
Indicates that one person became the next king of Hungary following another person in the royal succession.
-
D.
coronationAsKingOfHungary
Indicates the event or status of a person being formally crowned and installed as the king of Hungary.
-
E.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
- 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_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.