Triple

T19335253
Position Surface form Disambiguated ID Type / Status
Subject Giessen district E483605 entity
Predicate contains P35 FINISHED
Object Gießen NE NERFINISHED

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: Gießen | Statement: [Giessen district, contains, Gießen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gießen
Context triple: [Giessen district, contains, Gießen]
  • A. Gießen chosen
    Gießen is a mid-sized university city in central Germany known for its academic institutions and role as a regional administrative and cultural center.
  • B. Kassel
    Kassel is a city in central Germany known for its cultural institutions and as the host of the renowned contemporary art exhibition documenta.
  • C. Heilbronn
    Heilbronn is a city in the German state of Baden-Württemberg known for its industrial base, wine production, and role as a regional economic and educational hub.
  • D. Wetzlar
    Wetzlar is a historic German city in the state of Hesse, known for its medieval old town and its long tradition in optics and precision engineering.
  • E. Heppenheim
    Heppenheim is a historic town in southwestern Germany, known for its picturesque old town, vineyards, and location on the Bergstraße at the edge of the Odenwald.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61644b80c819080f9bca086424a36 completed April 20, 2026, 12:04 p.m.
Created at: April 10, 2026, 1:33 p.m.