Triple
T3424984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenceslaus IV of Bohemia |
E72207
|
entity |
| Predicate | startTime (reign as King of Bohemia) |
P1506
|
FINISHED |
| Object | 1378 |
—
|
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: 1378 | Statement: [Wenceslaus IV of Bohemia, startTime (reign as King of Bohemia), 1378]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime (reign as King of Bohemia) Context triple: [Wenceslaus IV of Bohemia, startTime (reign as King of Bohemia), 1378]
-
A.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
reignAsKingOfPolandStart
Indicates the time at which an entity begins its reign as king over Poland.
-
C.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
-
D.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
-
E.
reignAsHolyRomanEmperorStart
Indicates the time point or event at which an entity begins its tenure as Holy Roman Emperor.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb97fa2d88190a79cb8c7be4b3696 |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.