Triple
T28203364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Barnabas Church, Dibley |
E716947
|
entity |
| Predicate | usedForComicSituationsIn |
P157473
|
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: [St Barnabas Church, Dibley, usedForComicSituationsIn, The Vicar of Dibley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForComicSituationsIn Context triple: [St Barnabas Church, Dibley, usedForComicSituationsIn, The Vicar of Dibley]
-
A.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
B.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
C.
usesInComedy
chosen
Indicates that something is employed or incorporated as a humorous element within a comedic context or performance.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 10:33 p.m.