Triple
T13563589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles III Philip, Elector Palatine |
E323973
|
entity |
| Predicate | ruled |
P760
|
FINISHED |
| Object | Jülich-Berg |
E625677
|
NE 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: Jülich-Berg | Statement: [Charles III Philip, Elector Palatine, ruled, Jülich-Berg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jülich-Berg Context triple: [Charles III Philip, Elector Palatine, ruled, Jülich-Berg]
-
A.
Jülich-Berg
chosen
Jülich-Berg was a historical duchy in the Holy Roman Empire located in what is now western Germany, formed by the union of the territories of Jülich and Berg.
-
B.
Felsberg
Felsberg is a settlement located in the historical region of Westphalia in western Germany.
-
C.
Sendenhorst
Sendenhorst is a small town in the German state of North Rhine-Westphalia, known for its rural character and location in the Münsterland region.
-
D.
Meinisberg
Meinisberg is a small municipality in the canton of Bern in Switzerland, situated near the city of Biel/Bienne.
-
E.
Döbraberg
Döbraberg is the highest peak in Germany’s Franconian Forest range, known for its forested slopes and panoramic views.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bb1ef508190ab587bd2aa34795b |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.