Triple

T4538755
Position Surface form Disambiguated ID Type / Status
Subject Remagen E107474 entity
Predicate hasSubdivision P747 FINISHED
Object Unkelbach E378923 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: Unkelbach | Statement: [Remagen, hasSubdivision, Unkelbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Unkelbach
Context triple: [Remagen, hasSubdivision, Unkelbach]
  • A. Luterbach
    Luterbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Aare River.
  • B. Lüßbach
    Lüßbach is a small river in Bavaria, Germany, that serves as one of the tributaries feeding into Lake Starnberg.
  • C. Wahnbach chosen
    Wahnbach is a small river in North Rhine-Westphalia, Germany, known for feeding the Wahnbach Dam and serving as a tributary of the Sieg.
  • D. Breitenbach
    Breitenbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its location in the Thierstein district near the French border.
  • E. Schwarzenbach
    Schwarzenbach is a small river in Switzerland that serves as a tributary of the Murg.
  • 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_69bd43f922788190b7edfa294e39b178 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57ba327c8190a7f12e14077b1fa7 completed March 20, 2026, 2:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdc55ae8248190acda4f10eb5ce2e7 completed March 20, 2026, 10:08 p.m.
Created at: March 20, 2026, 1:04 p.m.