Triple

T7975746
Position Surface form Disambiguated ID Type / Status
Subject Andernach Geyser E185441 entity
Predicate locatedIn P40 FINISHED
Object Andernach E185441 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: Andernach | Statement: [Andernach Geyser, locatedIn, Andernach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andernach
Context triple: [Andernach Geyser, locatedIn, Andernach]
  • A. Andernach chosen
    Andernach is a historic German town on the Rhine River in Rhineland-Palatinate, known for its medieval architecture and one of the world’s highest cold-water geysers.
  • B. Neunkirchen
    Neunkirchen is a town in southwestern Germany known as one of the major urban centers and former industrial hubs of the state of Saarland.
  • C. Boppard
    Boppard is a historic town on the Rhine River in Germany, renowned for its well-preserved medieval architecture, wine culture, and scenic river landscapes.
  • D. Lohmar
    Lohmar is a town in the Rhein-Sieg district of North Rhine-Westphalia, Germany, situated near Cologne and known for its green surroundings and residential character.
  • E. Heinsberg
    Heinsberg is a town in western Germany’s North Rhine-Westphalia near the Dutch border, known as the administrative center of the Heinsberg district.
  • 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_69ca829851908190b4e03829353ee7c3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3bf56f688190902b95afe42635ec completed March 31, 2026, 3:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69ccbe086fc08190b41a2eb2193f6675 completed April 1, 2026, 6:41 a.m.
Created at: March 30, 2026, 5:14 p.m.