Triple
T28970005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dean of Coventry |
E734244
|
entity |
| Predicate | traditionallyResidesAt |
P78481
|
FINISHED |
| Object | the Deanery, Coventry |
—
|
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 Deanery, Coventry | Statement: [Dean of Coventry, traditionallyResidesAt, the Deanery, Coventry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyResidesAt Context triple: [Dean of Coventry, traditionallyResidesAt, the Deanery, Coventry]
-
A.
traditionallyResidesIn
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
-
B.
hasTraditionalResidenceType
Indicates that an entity is associated with a particular customary or historically established type of residence.
-
C.
hasTraditionalResidenceCountry
Indicates that an entity’s customary or long-term country of residence is the specified country.
-
D.
residencyAt
chosen
Indicates that an entity lives or has an established residence at a particular location or address.
-
E.
residencyOf
Indicates that one entity serves as the place where another entity resides or lives.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 28, 2026, 9:05 a.m.