Triple
T28604848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibley parish church |
E724015
|
entity |
| Predicate | primaryUseInNarrative |
P80898
|
FINISHED |
| Object | parish church of Dibley |
—
|
LITERAL FINISHED |
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: parish church of Dibley | Statement: [Dibley parish church, primaryUseInNarrative, parish church of Dibley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseInNarrative Context triple: [Dibley parish church, primaryUseInNarrative, parish church of Dibley]
-
A.
narrativePurpose
chosen
Indicates the role or function that something serves within the structure or progression of a narrative.
-
B.
narrativeCharacteristic
Indicates that one entity serves as a descriptive or defining narrative feature or quality of another entity.
-
C.
useInNarrative
Indicates that something is employed as an element or device within a narrative or story.
-
D.
narrativeImportance
Indicates the degree to which an entity or event is central, influential, or essential within the structure and progression of a narrative.
-
E.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
- 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_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: April 28, 2026, 4:26 a.m.