Triple

T32887407
Position Surface form Disambiguated ID Type / Status
Subject Cold Ash, Berkshire E841238 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object St Finian’s Church, Cold Ash
St Finian’s Church, Cold Ash is a Roman Catholic church serving the village of Cold Ash in Berkshire, England.
 E2026989 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 Finian’s Church, Cold Ash | Statement: [Cold Ash, Berkshire, hasReligiousBuilding, St Finian’s Church, Cold Ash]
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 Finian’s Church, Cold Ash
Triple: [Cold Ash, Berkshire, hasReligiousBuilding, St Finian’s Church, Cold Ash]
Generated description
St Finian’s Church, Cold Ash is a Roman Catholic church serving the village of Cold Ash in Berkshire, 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_69f349446e288190a70c05bcc4d81172 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d03fc90881908531538e7ba0a933 completed May 3, 2026, 4:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34c68691148190bafe6f8d3c97d565 completed June 19, 2026, 4:33 a.m.
NEDg Description generation batch_6a34c6e8dca08190add2e780968d9d1a completed June 19, 2026, 4:34 a.m.
NED2 Entity disambiguation (via description) batch_6a34c74670308190b0e7fbea7db0c164 completed June 19, 2026, 4:36 a.m.
Created at: May 1, 2026, 1:18 a.m.