Triple
T24782932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Saints Church, Broad Chalke |
E620048
|
entity |
| Predicate | belongsToBenefice |
P158113
|
FINISHED |
| Object | Chalke Valley benefice |
—
|
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: Chalke Valley benefice | Statement: [All Saints Church, Broad Chalke, belongsToBenefice, Chalke Valley benefice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToBenefice Context triple: [All Saints Church, Broad Chalke, belongsToBenefice, Chalke Valley benefice]
-
A.
beneficeType
Indicates the specific category or kind of benefice (ecclesiastical office or endowed church position) associated with an entity.
-
B.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
C.
relatedBenefit
Indicates that one entity provides an advantage, gain, or positive outcome that is connected or attributable to another entity.
-
D.
beneficiaryContribution
Indicates that one party provides a contribution, support, or resources that benefit another designated beneficiary.
-
E.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 4:45 a.m.