Triple
T32362680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl der Dicke |
E826906
|
entity |
| Predicate | RegierungszeitAlsKönigItaliens |
P29180
|
FINISHED |
| Object | 879–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: 879–887 | Statement: [Karl der Dicke, RegierungszeitAlsKönigItaliens, 879–887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RegierungszeitAlsKönigItaliens Context triple: [Karl der Dicke, RegierungszeitAlsKönigItaliens, 879–887]
-
A.
reignAsKingOfItalyEnd
Indicates the point in time or event at which an individual's reign as King of Italy comes to an end.
-
B.
reignAsKingOfItalyStart
chosen
Indicates the time at which a person begins their reign as king over Italy.
-
C.
successorAsKingOfItaly
Indicates that one person became the next king of Italy after another person.
-
D.
predecessorAsKingOfItaly
Indicates that one entity previously held the position of King of Italy immediately before another entity, establishing a direct succession in that royal office.
-
E.
coronationAsKingOfItaly
Indicates the event or relationship in which a person is formally crowned and invested with the title and authority of King of Italy.
- 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_69f6be9be6b48190b164c572650e8b95 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:49 a.m.