Triple

T6888019
Position Surface form Disambiguated ID Type / Status
Subject Duke of Jülich-Berg E158969 entity
Predicate hasJurisdictionOver P808 FINISHED
Object Jülich E690553 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 | Statement: [Duke of Jülich-Berg, hasJurisdictionOver, Jülich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jülich
Context triple: [Duke of Jülich-Berg, hasJurisdictionOver, Jülich]
  • A. Jülich chosen
    Jülich is a historic town in western Germany, known for its former status as a ducal residence and its significant Renaissance-era fortifications.
  • B. Lippstadt
    Lippstadt is a historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and role in regional conflicts.
  • C. Remscheid
    Remscheid is a city in North Rhine-Westphalia, Germany, known historically for its metalworking industry and as the birthplace of physicist Wilhelm Röntgen.
  • D. Kleve
    Kleve is a historic town in western Germany near the Dutch border, known for its medieval castle and role as the former capital of the Duchy of Cleves.
  • E. Recklinghausen
    Recklinghausen is a city in the Ruhr area of North Rhine-Westphalia, western Germany, known historically for coal mining and its role as a regional administrative center.
  • 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_69c9f798cbfc8190b1106298c3f211a5 completed March 30, 2026, 4:10 a.m.
Created at: March 27, 2026, 2:23 p.m.