Triple

T27115153
Position Surface form Disambiguated ID Type / Status
Subject Eggersdorf E686821 entity
Predicate partOf P40 FINISHED
Object Petershagen-Eggersdorf
Petershagen-Eggersdorf is a municipality in the Märkisch-Oderland district of Brandenburg, Germany, located east of Berlin and known as a residential commuter town.
E1757190 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: Petershagen-Eggersdorf | Statement: [Eggersdorf, partOf, Petershagen-Eggersdorf]
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: Petershagen-Eggersdorf
Triple: [Eggersdorf, partOf, Petershagen-Eggersdorf]
Generated description
Petershagen-Eggersdorf is a municipality in the Märkisch-Oderland district of Brandenburg, Germany, located east of Berlin and known as a residential commuter town.

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_69ef148c2b588190afc15b529f7af845 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f624059f7c8190b245dc53535a1ff2 completed May 2, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a124811f11881909ed52a475884b0b8 completed May 24, 2026, 12:36 a.m.
NEDg Description generation batch_6a1249280a048190bb0003079b8dfab4 completed May 24, 2026, 12:41 a.m.
NED2 Entity disambiguation (via description) batch_6a1249ea67c8819092a4905943bd6e0e completed May 24, 2026, 12:44 a.m.
Created at: April 27, 2026, 8:56 a.m.