Triple
T34127477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ Church, Washington Parish |
E875327
|
entity |
| Predicate | hasParishOrganization |
P196177
|
FINISHED |
| Object | vestry |
—
|
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: vestry | Statement: [Christ Church, Washington Parish, hasParishOrganization, vestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOrganization Context triple: [Christ Church, Washington Parish, hasParishOrganization, vestry]
-
A.
hasParishOrganisation
chosen
Indicates that an entity is associated with or administered by a specific parish-level organizational unit.
-
B.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
-
C.
hasParishNetwork
Indicates that an entity is connected to or served by a specific parish or group of parishes within an ecclesiastical or community network.
-
D.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
E.
haveOwnParishes
Indicates that an entity possesses or is responsible for its own distinct parishes.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 1, 2026, 1:53 a.m.