Triple

T32007079
Position Surface form Disambiguated ID Type / Status
Subject Neustadt an der Donau E817297 entity
Predicate hasSubdivision P747 FINISHED
Object Niederulrain
Niederulrain is a small locality that forms part of the town of Neustadt an der Donau in Bavaria, Germany.
E2005364 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: Niederulrain | Statement: [Neustadt an der Donau, hasSubdivision, Niederulrain]
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: Niederulrain
Triple: [Neustadt an der Donau, hasSubdivision, Niederulrain]
Generated description
Niederulrain is a small locality that forms part of the town of Neustadt an der Donau in Bavaria, Germany.

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_69f348f8ce388190ae84376b1f348f12 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b42a2b008190840c91c9b18857a7 completed May 3, 2026, 2:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a344eeb9c3881909fd3ad0c6658706e completed June 18, 2026, 8:02 p.m.
NEDg Description generation batch_6a34504a9d20819087cb7b137dd0565d completed June 18, 2026, 8:08 p.m.
NED2 Entity disambiguation (via description) batch_6a34512829448190912a57cc59c590ff completed June 18, 2026, 8:12 p.m.
Created at: May 1, 2026, 12:15 a.m.