Triple
T6593143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary’s Church, Hendon |
E148410
|
entity |
| Predicate | hasDenominationBranch |
P49186
|
FINISHED |
| Object | Anglicanism |
—
|
LITERAL 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: Anglicanism | Statement: [St. Mary’s Church, Hendon, hasDenominationBranch, Anglicanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDenominationBranch Context triple: [St. Mary’s Church, Hendon, hasDenominationBranch, Anglicanism]
-
A.
denominationBranch
chosen
Indicates that one religious organization or group is a subordinate branch, division, or subset of a larger religious denomination.
-
B.
hasFederallyRecognizedBranch
Indicates that an entity possesses at least one branch, division, or subsidiary that is officially recognized by a federal authority.
-
C.
denominationSharing
Indicates that two entities are associated with or use the same religious denomination or sect.
-
D.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
E.
includesDenomination
Indicates that one entity contains, comprises, or explicitly specifies a particular denomination as part of its definition or composition.
- 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_69c687e7b8688190811ffee72e096468 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acfd17388190bd0bb8b2371e7df1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.