Triple

T31495978
Position Surface form Disambiguated ID Type / Status
Subject Scheibbs District E803540 entity
Predicate hasMunicipality P847 FINISHED
Object Purgstall an der Erlauf
Purgstall an der Erlauf is a market town in Lower Austria known for its location along the Erlauf River and its historical and natural attractions.
E1967482 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: Purgstall an der Erlauf | Statement: [Scheibbs District, hasMunicipality, Purgstall an der Erlauf]
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: Purgstall an der Erlauf
Triple: [Scheibbs District, hasMunicipality, Purgstall an der Erlauf]
Generated description
Purgstall an der Erlauf is a market town in Lower Austria known for its location along the Erlauf River and its historical and natural attractions.

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_69f348cae52081909fa8e5f697523ae3 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a1ea029c8190ab83ffdf6a18caf8 completed May 3, 2026, 1:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b2d772794819080ebfe16dd9cf67b completed June 11, 2026, 9:49 p.m.
NEDg Description generation batch_6a2b30fe97088190b0b08ead4477f8c3 completed June 11, 2026, 10:04 p.m.
NED2 Entity disambiguation (via description) batch_6a2b31f1269c819091aa4845a9e32059 completed June 11, 2026, 10:08 p.m.
Created at: April 30, 2026, 9:41 p.m.