Triple
T30546128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Paul’s Episcopal Church, Watertown, New York |
E777420
|
entity |
| Predicate | hasClericalTradition |
P1186
|
FINISHED |
| Object | Anglican |
—
|
NE NERFINISHED |
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: Anglican | Statement: [St. Paul’s Episcopal Church, Watertown, New York, hasClericalTradition, Anglican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalTradition Context triple: [St. Paul’s Episcopal Church, Watertown, New York, hasClericalTradition, Anglican]
-
A.
hasRiteOrTradition
chosen
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
B.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
isRuledByClergy
Indicates that a group, region, or institution is governed or controlled by members of a religious clergy.
-
D.
theologicalTradition
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
E.
hasClericalDiscipline
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
- F. None of above.
Provenance (3 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 8:19 p.m.