Triple

T4288254
Position Surface form Disambiguated ID Type / Status
Subject Fürth Hardhöhe E97323 entity
Predicate serves P98 FINISHED
Object city of Fürth E213765 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: city of Fürth | Statement: [Fürth Hardhöhe, serves, city of Fürth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Fürth
Context triple: [Fürth Hardhöhe, serves, city of Fürth]
  • A. Stadt Fürth chosen
    Stadt Fürth is a Bavarian city in Germany known for its rich Franconian cultural traditions, historic architecture, and vibrant local festivals.
  • B. Stadt Nürnberg
    Stadt Nürnberg is the municipal government of the German city of Nuremberg, responsible for local administration, public services, and urban infrastructure.
  • C. Forchheim
    Forchheim is a town in Upper Franconia, Bavaria, Germany, known for its historic old town and location along major regional rail and road routes.
  • D. Ingolstadt
    Ingolstadt is a historic city in southern Germany known for its medieval architecture, university tradition, and role as a major hub of the automotive industry.
  • E. Schweinfurt
    Schweinfurt is a city in northern Bavaria, Germany, historically known for its ball bearing industry and as a strategic target during World War II.
  • 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_69b3454595848190a0e6bbb6a2bea040 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35060b70081908479c95b2afe8ec5 completed March 12, 2026, 11:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c72bec388190b03048507e2e6858 completed March 14, 2026, 8:38 p.m.
Created at: March 12, 2026, 11:08 p.m.