Triple
T25159365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John’s Smith Square |
E626398
|
entity |
| Predicate | religiousAffiliationWhenBuilt |
P17179
|
FINISHED |
| Object | Anglican |
—
|
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: Anglican | Statement: [St John’s Smith Square, religiousAffiliationWhenBuilt, Anglican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAffiliationWhenBuilt Context triple: [St John’s Smith Square, religiousAffiliationWhenBuilt, Anglican]
-
A.
religiousAffiliationAtFoundation
Indicates the religious denomination or tradition with which an entity was affiliated at the time it was founded.
-
B.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
C.
religionAtConstruction
chosen
Indicates the religion or religious tradition associated with something at the time it was constructed.
-
D.
associatedReligionBuilding
Indicates that there is a relationship between a religion and a specific building that is connected to, used by, or significant for that religion.
-
E.
religiousBuildingDedicatedTo
Indicates that a religious building is formally dedicated or consecrated to a particular deity, figure, or religious concept.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 6:31 a.m.