Triple

T32962798
Position Surface form Disambiguated ID Type / Status
Subject Orchardhill Parish Church E843284 entity
Predicate hasParish P35 FINISHED
Object Orchardhill Parish
Orchardhill Parish is a Church of Scotland parish community centered around Orchardhill Parish Church, serving the local area through worship and related activities.
E2031031 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: Orchardhill Parish | Statement: [Orchardhill Parish Church, hasParish, Orchardhill Parish]
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: Orchardhill Parish
Triple: [Orchardhill Parish Church, hasParish, Orchardhill Parish]
Generated description
Orchardhill Parish is a Church of Scotland parish community centered around Orchardhill Parish Church, serving the local area through worship and related activities.

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_69f3494af2808190ad98cec2f1bc0fe6 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d17b7a7c8190a00dd28fa8039a1c completed May 3, 2026, 4:39 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34d27ca66c819085564d42bd26d608 completed June 19, 2026, 5:24 a.m.
NEDg Description generation batch_6a34d3bdb6808190967b4c67d5a3af66 completed June 19, 2026, 5:29 a.m.
NED2 Entity disambiguation (via description) batch_6a34d46b4a4081909c03beb97142b28e completed June 19, 2026, 5:32 a.m.
Created at: May 1, 2026, 1:21 a.m.