Triple

T28763774
Position Surface form Disambiguated ID Type / Status
Subject Lieshout E726197 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object St Servatius Church
St Servatius Church is a historic Roman Catholic church in Lieshout, Netherlands, dedicated to Saint Servatius and serving as a central place of worship for the local community.
E1832873 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: St Servatius Church | Statement: [Lieshout, hasReligiousBuilding, St Servatius Church]
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: St Servatius Church
Triple: [Lieshout, hasReligiousBuilding, St Servatius Church]
Generated description
St Servatius Church is a historic Roman Catholic church in Lieshout, Netherlands, dedicated to Saint Servatius and serving as a central place of worship for the local community.

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_69f03198be14819098fa74e48b3749bf completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f65822594c8190b8c187c1f2fb4b8d completed May 2, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24a25f95108190b3616e74b56d8590 completed June 6, 2026, 10:42 p.m.
NEDg Description generation batch_6a24a7820d888190ba16b49e23c49d1c completed June 6, 2026, 11:04 p.m.
NED2 Entity disambiguation (via description) batch_6a24ab4ed6088190a8de9ed2255599ea completed June 6, 2026, 11:20 p.m.
Created at: April 28, 2026, 6:12 a.m.