Triple

T30025404
Position Surface form Disambiguated ID Type / Status
Subject Niederjosbach E762866 entity
Predicate hasWatercourse P165 FINISHED
Object Niederjosbach stream
The Niederjosbach stream is a small watercourse in Hesse, Germany, that flows through the village of Niederjosbach and its surrounding rural landscape.
E1897772 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: Niederjosbach stream | Statement: [Niederjosbach, hasWatercourse, Niederjosbach stream]
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: Niederjosbach stream
Triple: [Niederjosbach, hasWatercourse, Niederjosbach stream]
Generated description
The Niederjosbach stream is a small watercourse in Hesse, Germany, that flows through the village of Niederjosbach and its surrounding rural landscape.

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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f679aaeca88190b40cb982805443ad completed May 2, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27322f5e788190a35b290bcef65009 completed June 8, 2026, 9:20 p.m.
NEDg Description generation batch_6a27344392f8819096430da00dda75a1 completed June 8, 2026, 9:29 p.m.
NED2 Entity disambiguation (via description) batch_6a2734c2d13c8190b7401d9b7d6d8fed completed June 8, 2026, 9:31 p.m.
Created at: April 29, 2026, 6:48 p.m.