Triple

T19420841
Position Surface form Disambiguated ID Type / Status
Subject Gutach (Kinzig) E485847 entity
Predicate hasQualifier P13306 FINISHED
Object (Kinzig) 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: (Kinzig) | Statement: [Gutach (Kinzig), hasQualifier, (Kinzig)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: (Kinzig)
Context triple: [Gutach (Kinzig), hasQualifier, (Kinzig)]
  • A. Kinzig (Main) River
    The Kinzig (Main) River is a tributary of Germany’s Main River that flows through the state of Hesse, passing towns such as Hanau and Gelnhausen before joining the Main.
  • B. Karlinbach
    Karlinbach is a stream in South Tyrol, northern Italy, that serves as one of the inflowing watercourses to Lake Resia in the Alpine region.
  • C. Kinzig chosen
    The Kinzig is a river in southwestern Germany that flows through the Black Forest region before joining the Rhine.
  • D. Eckersbach
    Eckersbach is a district of the city of Zwickau in the German state of Saxony, known primarily as a residential area.
  • E. Enkenbach
    Enkenbach is a locality in the German state of Rhineland-Palatinate, situated near Kaiserslautern and served by regional rail connections.
  • 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63214d768819082129100d7116521 completed April 20, 2026, 2:03 p.m.
Created at: April 10, 2026, 1:37 p.m.