Triple

T29532875
Position Surface form Disambiguated ID Type / Status
Subject Wannweil E749253 entity
Predicate hasNeighbouringMunicipality P224 FINISHED
Object Kirchentellinsfurt
Kirchentellinsfurt is a small municipality in the district of Tübingen in Baden-Württemberg, southwestern Germany, situated near the Neckar River.
E1926579 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: Kirchentellinsfurt | Statement: [Wannweil, hasNeighbouringMunicipality, Kirchentellinsfurt]
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: Kirchentellinsfurt
Triple: [Wannweil, hasNeighbouringMunicipality, Kirchentellinsfurt]
Generated description
Kirchentellinsfurt is a small municipality in the district of Tübingen in Baden-Württemberg, southwestern Germany, situated near the Neckar River.

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_69f0bd47abb081909bd6e6a33d770fd8 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66cc3679c8190be65a057a4c6502d completed May 2, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2870c6f90881908e4bc0adf838efcd completed June 9, 2026, 8 p.m.
NEDg Description generation batch_6a2876382fc881908f4c656e46bb4645 completed June 9, 2026, 8:23 p.m.
NED2 Entity disambiguation (via description) batch_6a28768f0df08190bb21a885a9d1fdb4 completed June 9, 2026, 8:24 p.m.
Created at: April 28, 2026, 4:55 p.m.