Triple

T8200673
Position Surface form Disambiguated ID Type / Status
Subject Linn E191563 entity
Predicate partOf P40 FINISHED
Object Krefeld E398502 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: Krefeld | Statement: [Linn, partOf, Krefeld]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krefeld
Context triple: [Linn, partOf, Krefeld]
  • A. Krefeld chosen
    Krefeld is a city in western Germany near the Rhine River, known historically for its textile and silk industry.
  • B. Düsseldorf
    Düsseldorf is a major German city on the Rhine River known for its fashion and art scenes, modern architecture, and status as an important economic and financial center.
  • C. Duisburg
    Duisburg is a major industrial and port city in western Germany’s Ruhr region, known for its steel production and one of the world’s largest inland harbors.
  • D. 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.
  • E. Mülheim an der Ruhr
    Mülheim an der Ruhr is a city in western Germany’s Ruhr area, known for its industrial heritage, riverside setting on the Ruhr River, and role as a regional economic and cultural 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_69ca82c6e9548190a4c5ca14516e4417 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb5df565dc819099537fc06b694b40 completed March 31, 2026, 5:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69d181f4123c8190a15ee03b3156c6fd completed April 4, 2026, 9:26 p.m.
Created at: March 30, 2026, 5:43 p.m.