Triple
T28604862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibley parish church |
E724015
|
entity |
| Predicate | centralSettingIn |
P4751
|
FINISHED |
| Object | The Vicar of Dibley |
—
|
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: The Vicar of Dibley | Statement: [Dibley parish church, centralSettingIn, The Vicar of Dibley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralSettingIn Context triple: [Dibley parish church, centralSettingIn, The Vicar of Dibley]
-
A.
centralSet
Indicates that the referenced set occupies a central or core position within a larger structure, system, or collection, often serving as a primary or focal subset.
-
B.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
-
D.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an entity.
-
E.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 4:26 a.m.