Triple
T14077163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ditton |
E338764
|
entity |
| Predicate | isPartOfParishSystem |
P85718
|
FINISHED |
| Object | Church of England parish structure |
—
|
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: Church of England parish structure | Statement: [Ditton, isPartOfParishSystem, Church of England parish structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfParishSystem Context triple: [Ditton, isPartOfParishSystem, Church of England parish structure]
-
A.
usesParishSystem
chosen
Indicates that an entity organizes its local governance, administration, or jurisdiction according to a parish-based system.
-
B.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
C.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
D.
hasRuralParish
Indicates that an entity possesses or is associated with a rural parish as an administrative or ecclesiastical subdivision.
-
E.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5cdd288190914e1d57321b3554 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.