Triple

T16653432
Position Surface form Disambiguated ID Type / Status
Subject Lauffen am Neckar E404663 entity
Predicate locatedNear P294 FINISHED
Object Heilbronn 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: Heilbronn | Statement: [Lauffen am Neckar, locatedNear, Heilbronn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heilbronn
Context triple: [Lauffen am Neckar, locatedNear, Heilbronn]
  • A. Heilbronn chosen
    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.
  • B. Karlsruhe
    Karlsruhe is a major city in southwestern Germany best known as the seat of the country’s highest courts and a central hub of German constitutional jurisprudence.
  • C. Ulm
    Ulm is a historic city in the German state of Baden-Württemberg, best known for its towering Gothic cathedral and as the birthplace of physicist Albert Einstein.
  • D. 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.
  • E. Göppingen
    Göppingen is a town in the German state of Baden-Württemberg known as an industrial and administrative center in the Filstal valley near Stuttgart.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37bf861348190b2b0b5574d4ddb4f completed April 18, 2026, 12:41 p.m.
Created at: April 10, 2026, 5:18 a.m.