Triple
T7170980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry VI, Holy Roman Emperor |
E167193
|
entity |
| Predicate | coronationAsKingOfSicilyDate |
P59579
|
FINISHED |
| Object | 1194-12-25 |
—
|
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: 1194-12-25 | Statement: [Henry VI, Holy Roman Emperor, coronationAsKingOfSicilyDate, 1194-12-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationAsKingOfSicilyDate Context triple: [Henry VI, Holy Roman Emperor, coronationAsKingOfSicilyDate, 1194-12-25]
-
A.
coronationAsKingOfSicily
chosen
Indicates the event or relationship in which an individual is formally crowned and invested with the royal title and authority as King of Sicily.
-
B.
reignAsKingOfSicilyStart
Indicates the time at which an individual begins their reign as king over the realm of Sicily.
-
C.
reignAsKingOfSicilyEnd
Indicates the point in time or event at which an individual's reign as king of Sicily comes to an end.
-
D.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
E.
successorAsKingOfSicily
Indicates that one person became the next king of Sicily after another person.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85ec718819085af59fadee9d22d |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.