Triple

T31282305
Position Surface form Disambiguated ID Type / Status
Subject Pöhlde Abbey E797703 entity
Predicate locatedIn P40 FINISHED
Object Pöhlde
Pöhlde is a village in Lower Saxony, Germany, historically notable for its medieval abbey and long-standing religious heritage.
E1981610 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: Pöhlde | Statement: [Pöhlde Abbey, locatedIn, Pöhlde]
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: Pöhlde
Triple: [Pöhlde Abbey, locatedIn, Pöhlde]
Generated description
Pöhlde is a village in Lower Saxony, Germany, historically notable for its medieval abbey and long-standing religious heritage.

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_69f224def9088190a37034eab3daf57f completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69e00bbe88190b8e807d2a9522bc2 completed May 3, 2026, 12:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e7fbb45848190b4bec5a823ffffa0 completed June 14, 2026, 10:17 a.m.
NEDg Description generation batch_6a2e802f7d2c8190aaffa40b02fb55ee completed June 14, 2026, 10:19 a.m.
NED2 Entity disambiguation (via description) batch_6a2e809327288190a871aa12778550b9 completed June 14, 2026, 10:21 a.m.
Created at: April 29, 2026, 9:13 p.m.