Triple
T32362683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl der Dicke |
E826906
|
entity |
| Predicate | RegierungszeitAlsKönigWestfrankens |
P90981
|
FINISHED |
| Object | 884–887 |
—
|
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: 884–887 | Statement: [Karl der Dicke, RegierungszeitAlsKönigWestfrankens, 884–887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RegierungszeitAlsKönigWestfrankens Context triple: [Karl der Dicke, RegierungszeitAlsKönigWestfrankens, 884–887]
-
A.
reignAsKingOfTheFranksEnd
Indicates the point in time or event at which an entity’s reign as king of the Franks comes to an end.
-
B.
reignEndAsKingOfWestFrancia
chosen
Indicates the date or event when an individual’s reign as king of West Francia came to an end.
-
C.
successorAsKingOfWestFrancia
Indicates that one person became the next king of West Francia after another person, directly following them in that royal succession.
-
D.
reignEndAsKingOfAustrasia
Indicates the time or event at which an individual's reign as king of Austrasia comes to an end.
-
E.
predecessorAsKingOfWestFrancia
Indicates that one entity served as the immediately preceding king of West Francia relative to another entity.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:49 a.m.