Triple

T31802339
Position Surface form Disambiguated ID Type / Status
Subject Prüm E811773 entity
Predicate hasParish P35 FINISHED
Object Catholic parish of Prüm
The Catholic parish of Prüm is a Roman Catholic ecclesiastical community centered in the town of Prüm in western Germany, historically linked to the former Benedictine abbey there.
E811774 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: Catholic parish of Prüm | Statement: [Prüm, hasParish, Catholic parish of Prüm]
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: Catholic parish of Prüm
Triple: [Prüm, hasParish, Catholic parish of Prüm]
Generated description
The Catholic parish of Prüm is a Roman Catholic ecclesiastical community centered in the town of Prüm in western Germany, historically linked to the former Benedictine abbey there.

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_69f348e70d188190b4637c5509f81274 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6acac7b648190aefb88517ac69829 completed May 3, 2026, 2:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2d9d68ac048190a73f49d8f3339007 completed June 13, 2026, 6:11 p.m.
NEDg Description generation batch_6a2da13c1c888190aba53c9271361316 completed June 13, 2026, 6:28 p.m.
NED2 Entity disambiguation (via description) batch_6a2da20c4e8c8190ac196a8a086cd3c1 completed June 13, 2026, 6:31 p.m.
Created at: April 30, 2026, 11:42 p.m.