Triple

T34666580
Position Surface form Disambiguated ID Type / Status
Subject Saint James Windward Parish E890272 entity
Predicate hasParishChurch P1191 FINISHED
Object Saint James Anglican Church
Saint James Anglican Church is the principal Anglican place of worship serving the community of Saint James Windward Parish.
E2108515 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: Saint James Anglican Church | Statement: [Saint James Windward Parish, hasParishChurch, Saint James Anglican 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: Saint James Anglican Church
Triple: [Saint James Windward Parish, hasParishChurch, Saint James Anglican Church]
Generated description
Saint James Anglican Church is the principal Anglican place of worship serving the community of Saint James Windward Parish.

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_69f349d9c59481908b36baa0be093aea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f722f81fc48190bed78b48e86e15e2 completed May 3, 2026, 10:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3752eae3988190be9c25673bc089e2 completed June 21, 2026, 2:56 a.m.
NEDg Description generation batch_6a3755ba184c8190877047d91813ec62 completed June 21, 2026, 3:08 a.m.
NED2 Entity disambiguation (via description) batch_6a37564ad39c81909d72314411b2e41c completed June 21, 2026, 3:11 a.m.
Created at: May 1, 2026, 2:05 a.m.