Triple
T29656415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furness Abbey |
E750278
|
entity |
| Predicate | dioceseDuringMonasticPeriod |
P167572
|
FINISHED |
| Object | Diocese of York |
—
|
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: Diocese of York | Statement: [Furness Abbey, dioceseDuringMonasticPeriod, Diocese of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseDuringMonasticPeriod Context triple: [Furness Abbey, dioceseDuringMonasticPeriod, Diocese of York]
-
A.
dioceseEstablishedBefore
Indicates that one diocese was formally established at an earlier date than another diocese.
-
B.
historicalEraOfMonastery
Indicates the historical era or period during which the monastery was founded, active, or most prominently associated.
-
C.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
D.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
E.
hasDioceseHistory
Indicates that an entity has an associated historical record or account of its diocese, including its past developments, changes, or events.
- F. None of above. chosen
Provenance (4 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f2850288190a394272ae49084e3 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:55 p.m.