Triple

T23471773
Position Surface form Disambiguated ID Type / Status
Subject Neckar-Odenwald-Kreis E570147 entity
Predicate hasMunicipality P847 FINISHED
Object Neckargerach
Neckargerach is a small municipality in the Neckar valley of southwestern Germany, known for its scenic location between the Odenwald hills and the river Neckar.
E1593597 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: Neckargerach | Statement: [Neckar-Odenwald-Kreis, hasMunicipality, Neckargerach]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Neckargerach
Triple: [Neckar-Odenwald-Kreis, hasMunicipality, Neckargerach]
Generated description
Neckargerach is a small municipality in the Neckar valley of southwestern Germany, known for its scenic location between the Odenwald hills and the river Neckar.

Provenance (5 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_69e245af8a88819084f2704f6d265a92 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a700bd0481908047aa4678217cbd completed April 29, 2026, 6:36 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f454bfe68819081e87c6dc6af4540 completed May 21, 2026, 5:47 p.m.
NEDg Description generation batch_6a0f46b69d288190b3fb6dcea9fb44b5 completed May 21, 2026, 5:53 p.m.
NED2 Entity disambiguation (via description) batch_6a0f479575a48190a63dd376b8fec617 completed May 21, 2026, 5:57 p.m.
Created at: April 17, 2026, 5:55 p.m.