Triple
T28780312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindsey’s Essex Street Chapel congregation |
E726657
|
entity |
| Predicate | foundedByClergyFrom |
P189431
|
FINISHED |
| Object | Church of England |
—
|
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: Church of England | Statement: [Lindsey’s Essex Street Chapel congregation, foundedByClergyFrom, Church of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedByClergyFrom Context triple: [Lindsey’s Essex Street Chapel congregation, foundedByClergyFrom, Church of England]
-
A.
parishFoundedBy
Indicates that a parish was established or created by a specific person or organization.
-
B.
founderReligiousOrder
Indicates that a person established or created a particular religious order.
-
C.
founderOfOrder
Indicates that an entity established or created a particular order, organization, or structured group.
-
D.
hasReligiousFounderAssociated
Indicates that an entity is associated with a specific religious founder, typically through origin, dedication, or foundational influence.
-
E.
foundedChurchesIn
Indicates that an entity established or created one or more churches in a specified location or context.
- F. None of above. chosen
Provenance (4 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 28, 2026, 6:19 a.m.