Triple
T33861760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compton Wynyates |
E867941
|
entity |
| Predicate | parishChurchNearby |
P148833
|
FINISHED |
| Object | Church of St Mary, Compton Wynyates |
—
|
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: Church of St Mary, Compton Wynyates | Statement: [Compton Wynyates, parishChurchNearby, Church of St Mary, Compton Wynyates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchNearby Context triple: [Compton Wynyates, parishChurchNearby, Church of St Mary, Compton Wynyates]
-
A.
locatesChurchWithin
Indicates that one entity places or establishes a church within the boundaries or interior of another entity.
-
B.
parishChurchLocation
chosen
Indicates the specific place where a parish church is situated or located.
-
C.
parishChurchName
Indicates the name of the parish church associated with a given entity.
-
D.
nearParish
Indicates that one entity is geographically close to or in the vicinity of a specified parish.
-
E.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.