Triple
T31202926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godfrey III, Count of Louvain |
E795522
|
entity |
| Predicate | reignEndAsDukeOfLowerLotharingia |
P181163
|
FINISHED |
| Object | 1190 |
—
|
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: 1190 | Statement: [Godfrey III, Count of Louvain, reignEndAsDukeOfLowerLotharingia, 1190]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignEndAsDukeOfLowerLotharingia Context triple: [Godfrey III, Count of Louvain, reignEndAsDukeOfLowerLotharingia, 1190]
-
A.
reignAsDukeOfLowerLotharingiaStart
Indicates the point in time when an individual begins their tenure reigning as Duke of Lower Lotharingia.
-
B.
reignEndAsKingOfEastFrancia
Indicates the time or event at which an individual’s rule as king over East Francia comes to an end.
-
C.
reignEndAsKingOfAustrasia
Indicates the time or event at which an individual's reign as king of Austrasia comes to an end.
-
D.
reignAsDukeOfLorraineEnd
Indicates the time or event at which an individual’s tenure or rule as Duke of Lorraine comes to an end.
-
E.
reignEndAsKingOfWestFrancia
Indicates the date or event when an individual’s reign as king of West Francia came 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 29, 2026, 9:09 p.m.