Triple

T30111531
Position Surface form Disambiguated ID Type / Status
Subject Wendron E765288 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Parish church of St Wendrona
The Parish Church of St Wendrona is a historic Anglican church serving the rural community of Wendron in Cornwall, England.
E1899980 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: Parish church of St Wendrona | Statement: [Wendron, hasReligiousBuilding, Parish church of St Wendrona]
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: Parish church of St Wendrona
Triple: [Wendron, hasReligiousBuilding, Parish church of St Wendrona]
Generated description
The Parish Church of St Wendrona is a historic Anglican church serving the rural community of Wendron in Cornwall, England.

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_69f22475ad7c8190be7f9541044a0bbb completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67dbfc82081909ae5d04676627a6c completed May 2, 2026, 10:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2743376c808190a6bc89154bc0a8f2 completed June 8, 2026, 10:33 p.m.
NEDg Description generation batch_6a2743bb3a8081908e963d8e8f4a9abc completed June 8, 2026, 10:35 p.m.
NED2 Entity disambiguation (via description) batch_6a2744c1a1d881908e1e9a00a065a253 completed June 8, 2026, 10:40 p.m.
Created at: April 29, 2026, 7:10 p.m.