Triple
T21523655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Chessun |
E531037
|
entity |
| Predicate | incumbency |
P136050
|
FINISHED |
| Object | Rector of St Dunstan’s, Cranbrook |
—
|
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: Rector of St Dunstan’s, Cranbrook | Statement: [Christopher Chessun, incumbency, Rector of St Dunstan’s, Cranbrook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incumbency Context triple: [Christopher Chessun, incumbency, Rector of St Dunstan’s, Cranbrook]
-
A.
incumbent
Indicates that an entity currently holds a particular position, office, or role at the present time.
-
B.
incumbentOffice
Indicates that a person currently holds and serves in a specified office or position.
-
C.
incumbentPosition
chosen
Indicates that a person currently holds or occupies a specific position, office, or role.
-
D.
incumbentOutcome
Indicates the result or consequence experienced by the current officeholder or position-holder in a given event or context.
-
E.
backedIncumbent
Indicates that a person or organization provided support to the current officeholder or existing position-holder, typically in a political or competitive 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884f4504819086bd632e62f02f58 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.