Triple
T1563425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold II, Holy Roman Emperor |
E33377
|
entity |
| Predicate | coronationAsKingOfBohemiaDate |
P1508
|
FINISHED |
| Object | 1791-09-06 |
—
|
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: 1791-09-06 | Statement: [Leopold II, Holy Roman Emperor, coronationAsKingOfBohemiaDate, 1791-09-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationAsKingOfBohemiaDate Context triple: [Leopold II, Holy Roman Emperor, coronationAsKingOfBohemiaDate, 1791-09-06]
-
A.
successorAsKingOfBohemia
Indicates that one person became the next king of Bohemia after another person.
-
B.
coronationDate
chosen
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
C.
predecessorAsKingOfBohemia
Indicates that one entity was the immediately preceding holder of the kingship of Bohemia relative to another entity.
-
D.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
E.
coronationPlaceAsHolyRomanEmperor
Indicates the place where a person was ceremonially crowned 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.