Triple
T32362700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl der Dicke |
E826906
|
entity |
| Predicate | vereinigteVorübergehend |
P7838
|
FINISHED |
| Object | große Teile des Karolingerreiches |
—
|
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: große Teile des Karolingerreiches | Statement: [Karl der Dicke, vereinigteVorübergehend, große Teile des Karolingerreiches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vereinigteVorübergehend Context triple: [Karl der Dicke, vereinigteVorübergehend, große Teile des Karolingerreiches]
-
A.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
usedBriefly
Indicates that an entity made short-term or momentary use of another entity or resource.
-
C.
wasUnifiedWith
chosen
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
oftenUnitedWith
Indicates that two entities are frequently joined, combined, or associated together as a common or recurring unit.
-
E.
temporarilyAbolished
Indicates that a rule, institution, practice, or status has been officially suspended or done away with for a limited period of time rather than permanently.
- 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.