Triple
T32570819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennington |
E832507
|
entity |
| Predicate | establishedAsParish |
P153991
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Kennington, establishedAsParish, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsParish Context triple: [Kennington, establishedAsParish, 2019]
-
A.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
B.
isHistoricParishOf
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
C.
hasParishStatusSince
chosen
Indicates that an entity has held the status of a parish continuously starting from a specified point in time.
-
D.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
E.
hasLongStandingParishCommunity
Indicates that an entity has been associated with an established parish community over a long period of time.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:03 a.m.