Triple

T38362089
Position Surface form Disambiguated ID Type / Status
Subject Langdorf E892318 entity
Predicate partOf P40 FINISHED
Object Verwaltungsgemeinschaft Regen
Verwaltungsgemeinschaft Regen is an administrative community in the Bavarian district of Regen, Germany, that jointly manages local government functions for several nearby municipalities.
E2266055 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: Verwaltungsgemeinschaft Regen | Statement: [Langdorf, partOf, Verwaltungsgemeinschaft Regen]
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: Verwaltungsgemeinschaft Regen
Triple: [Langdorf, partOf, Verwaltungsgemeinschaft Regen]
Generated description
Verwaltungsgemeinschaft Regen is an administrative community in the Bavarian district of Regen, Germany, that jointly manages local government functions for several nearby municipalities.

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_69f76e47cb4c8190bdd92cd1db59c0c5 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcc73b81b48190885831804bdd30f0 completed May 7, 2026, 5:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41a801831c8190b5d47fea007a987a completed June 28, 2026, 11:02 p.m.
NEDg Description generation batch_6a41a8f8ff04819087c4b80f8de32b81 completed June 28, 2026, 11:06 p.m.
NED2 Entity disambiguation (via description) batch_6a41a9aecf108190a0833bde27cb0e6a completed June 28, 2026, 11:09 p.m.
Created at: May 3, 2026, 4:31 p.m.