Triple

T26727492
Position Surface form Disambiguated ID Type / Status
Subject Muirkirk E673871 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Muirkirk Parish Church
Muirkirk Parish Church is a historic Christian church serving as the main place of worship for the local community in the village of Muirkirk, Scotland.
E1740603 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: Muirkirk Parish Church | Statement: [Muirkirk, hasReligiousBuilding, Muirkirk Parish 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: Muirkirk Parish Church
Triple: [Muirkirk, hasReligiousBuilding, Muirkirk Parish Church]
Generated description
Muirkirk Parish Church is a historic Christian church serving as the main place of worship for the local community in the village of Muirkirk, Scotland.

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_69eecda481d08190aea69f2f7c745f56 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f6180c6ba081908b82e0a76fdb94e8 completed May 2, 2026, 3:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12093f66a4819084efa818822737bf completed May 23, 2026, 8:08 p.m.
NEDg Description generation batch_6a1209d4ee448190b8e3d8cdb44fc641 completed May 23, 2026, 8:11 p.m.
NED2 Entity disambiguation (via description) batch_6a120a4736688190939a60d04fe467e2 completed May 23, 2026, 8:12 p.m.
Created at: April 27, 2026, 3:43 a.m.