Triple
T13847438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothair III, Holy Roman Emperor |
E332843
|
entity |
| Predicate | reignAsDukeOfSaxonyEnd |
P111738
|
FINISHED |
| Object | 1137 |
—
|
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: 1137 | Statement: [Lothair III, Holy Roman Emperor, reignAsDukeOfSaxonyEnd, 1137]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsDukeOfSaxonyEnd Context triple: [Lothair III, Holy Roman Emperor, reignAsDukeOfSaxonyEnd, 1137]
-
A.
reignAsDukeOfSwabiaEnd
Indicates the point in time or event at which an individual's tenure or rule as Duke of Swabia comes to an end.
-
B.
reignAsDukeOfBavariaFrom
Indicates that a person held and exercised the title and authority of Duke of Bavaria starting from a specified time.
-
C.
reignAsDukeOfBavariaTo
Indicates that one entity holds and exercises the title and authority of Duke of Bavaria over another entity (typically a territory or domain).
-
D.
reignEndAsDukeOfAustria
Indicates the time or event at which an individual’s rule in the role of Duke of Austria comes to an end.
-
E.
reignAsGrandDukeOfTuscanyEnd
Indicates the time or event at which an individual’s tenure as Grand Duke of Tuscany 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b2a9788190b164760adec64ef6 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:14 p.m.