Triple
T33672364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroer |
E862651
|
entity |
| Predicate | belongsToEcclesiasticalParish |
P139264
|
FINISHED |
| Object | Kroer parish |
—
|
NE NERFINISHED |
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: Kroer parish | Statement: [Kroer, belongsToEcclesiasticalParish, Kroer parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToEcclesiasticalParish Context triple: [Kroer, belongsToEcclesiasticalParish, Kroer parish]
-
A.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
B.
hasParishStatusInChurchOfEngland
Indicates that an entity holds official parish status within the organizational structure of the Church of England.
-
C.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
D.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
E.
hasReligiousParishCentre
chosen
Indicates that an entity has, is associated with, or is served by a specific religious parish center.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:43 a.m.