Triple

T16381242
Position Surface form Disambiguated ID Type / Status
Subject Soest district E397811 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Lippstadt E567830 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: Lippstadt | Statement: [Soest district, containsAdministrativeTerritorialEntity, Lippstadt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lippstadt
Context triple: [Soest district, containsAdministrativeTerritorialEntity, Lippstadt]
  • A. Lippstadt chosen
    Lippstadt is a historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and role in regional conflicts.
  • B. Nordhorn
    Nordhorn is a town in Lower Saxony, Germany, known as the administrative center of the Grafschaft Bentheim district near the Dutch border.
  • 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. Jülich
    Jülich is a historic town in western Germany, known for its former status as a ducal residence and its significant Renaissance-era fortifications.
  • E. Gardelegen
    Gardelegen is a historic town in the German state of Saxony-Anhalt, known for its medieval architecture and its location in the Altmark region.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319dd0e0c8190812bde6a2f7d9644 completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a023005e760819081b723a7246c78ce completed May 11, 2026, 7:37 p.m.
Created at: April 10, 2026, 5:08 a.m.