Triple

T31521432
Position Surface form Disambiguated ID Type / Status
Subject Bordenau E804215 entity
Predicate locatedIn P40 FINISHED
Object Neustadt am Rübenberge
Neustadt am Rübenberge is a town in Lower Saxony, Germany, situated northwest of Hanover and known for its surrounding rural villages and proximity to the Steinhuder Meer.
E1999910 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: Neustadt am Rübenberge | Statement: [Bordenau, locatedIn, Neustadt am Rübenberge]
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: Neustadt am Rübenberge
Triple: [Bordenau, locatedIn, Neustadt am Rübenberge]
Generated description
Neustadt am Rübenberge is a town in Lower Saxony, Germany, situated northwest of Hanover and known for its surrounding rural villages and proximity to the Steinhuder Meer.

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_69f348cf839c81908657048402f7f97b completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a75bfce48190970d785832a96ed3 completed May 3, 2026, 1:39 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2f46af79f08190b633ad7b64d5f07e completed June 15, 2026, 12:26 a.m.
NEDg Description generation batch_6a2f7243c45c8190aeaf62aa9717aae3 completed June 15, 2026, 3:32 a.m.
NED2 Entity disambiguation (via description) batch_6a2f72bc08948190a0292ca236b7b7f8 completed June 15, 2026, 3:34 a.m.
Created at: April 30, 2026, 9:56 p.m.