Triple
T19891035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Cuthbert's Church, Edinburgh |
E478029
|
entity |
| Predicate | parishOriginatesFromCentury |
P75550
|
FINISHED |
| Object | 7th century |
—
|
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: 7th century | Statement: [St Cuthbert's Church, Edinburgh, parishOriginatesFromCentury, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishOriginatesFromCentury Context triple: [St Cuthbert's Church, Edinburgh, parishOriginatesFromCentury, 7th century]
-
A.
parishEstablished
Indicates that a parish was formally created or founded at a specific time or under specific authority.
-
B.
parishChurchCentury
chosen
Indicates the century during which a given parish church was established, built, or primarily dates from.
-
C.
parishFoundedBy
Indicates that a parish was established or created by a specific person or organization.
-
D.
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.
-
E.
hasParishHistory
Indicates that an entity possesses or is associated with a documented historical record of a parish.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590e02388190ab82918750cc2647 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.