Triple
T32362681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl der Dicke |
E826906
|
entity |
| Predicate | RegierungszeitAlsRömischerKaiser |
P125451
|
FINISHED |
| Object | 881–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: 881–887 | Statement: [Karl der Dicke, RegierungszeitAlsRömischerKaiser, 881–887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RegierungszeitAlsRömischerKaiser Context triple: [Karl der Dicke, RegierungszeitAlsRömischerKaiser, 881–887]
-
A.
underRomanEmperor
Indicates that one entity existed, occurred, or was governed during the reign of the specified Roman emperor.
-
B.
wasEmperorDuring
chosen
Indicates that a person held the position of emperor during a specified time period or historical era.
-
C.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
D.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
E.
issuedDuringReignOf
Indicates that something (such as a document, decree, or coin) was formally issued while a particular ruler or authority was in power.
- 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_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:49 a.m.