Triple
T6888020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Jülich-Berg |
E158969
|
entity |
| Predicate | hasJurisdictionOver |
P808
|
FINISHED |
| Object | Berg |
E287565
|
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: Berg | Statement: [Duke of Jülich-Berg, hasJurisdictionOver, Berg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berg Context triple: [Duke of Jülich-Berg, hasJurisdictionOver, Berg]
-
A.
Berg
chosen
Berg was a historical German territorial entity that gave its name to the later Grand Duchy of Berg in the Rhineland region.
-
B.
Berg
Berg is a small town in eastern Luxembourg that serves as the administrative center of the commune of Betzdorf.
-
C.
Berghaupten
Berghaupten is a small municipality in the Ortenau district of Baden-Württemberg in southwestern Germany, known for its scenic location in the Black Forest region.
-
D.
Wilseder Berg
Wilseder Berg is a prominent hill and popular viewpoint in northern Germany, known for its scenic heathland landscapes within the Lüneburg Heath region.
-
E.
Hoche
Hoche is a Paris Métro station located in the northeastern suburb of Pantin, serving as a stop on the city’s Line 5.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d9101e30819084695ba0003a255c |
completed | March 27, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742e249508190ac95be97c0409d4a |
completed | March 28, 2026, 2:54 a.m. |
Created at: March 27, 2026, 2:23 p.m.