Triple
T35296230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereford Deanery |
E1019376
|
entity |
| Predicate | hasTypeOfParishStructure |
P13874
|
FINISHED |
| Object | benefices and parishes |
—
|
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: benefices and parishes | Statement: [Hereford Deanery, hasTypeOfParishStructure, benefices and parishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfParishStructure Context triple: [Hereford Deanery, hasTypeOfParishStructure, benefices and parishes]
-
A.
hasParishType
chosen
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
B.
hasParishOrganisation
Indicates that an entity is associated with or administered by a specific parish-level organizational unit.
-
C.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
D.
hasCivilParishComponent
Indicates that an entity includes or is composed of the specified civil parish as one of its administrative components.
-
E.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:03 p.m.