Triple
T28203702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibley Parish Council |
E716956
|
entity |
| Predicate | notableClerk |
P1918
|
FINISHED |
| Object | Frank Pickle |
—
|
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: Frank Pickle | Statement: [Dibley Parish Council, notableClerk, Frank Pickle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClerk Context triple: [Dibley Parish Council, notableClerk, Frank Pickle]
-
A.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
-
B.
notableRetainer
Indicates that one entity serves as a distinguished or prominent retainer, attendant, or subordinate to another entity.
-
C.
notableProsecutor
Indicates that the person served as a prosecutor in a way that is widely recognized as significant or noteworthy.
-
D.
notableHolder
chosen
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
E.
notableWitness
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
- 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_6a00a094c44c81908e4501151688a635 |
completed | May 10, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a009fcdfd848190841deaad9667d347 |
completed | May 10, 2026, 3:10 p.m. |
Created at: April 27, 2026, 10:33 p.m.