Triple
T17131957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of England parish church of Saint James the Great |
E415739
|
entity |
| Predicate | villageChurch |
P126225
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Church of England parish church of Saint James the Great, villageChurch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: villageChurch Context triple: [Church of England parish church of Saint James the Great, villageChurch, true]
-
A.
hasVillageChurchCharacter
Indicates that something possesses the qualities or characteristics typically associated with a village church.
-
B.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
C.
religiousSettlement
Indicates a settlement whose primary purpose, identity, or function is organized around religious life, practice, or institutions.
-
D.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
E.
hasParishChurchesIn
Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02a9fbc81909d820d29417aa55c |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.