Triple
T34809999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramsey Abbey |
E1003470
|
entity |
| Predicate | dioceseHistorically |
P134822
|
FINISHED |
| Object | Diocese of Lincoln |
—
|
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 Lincoln | Statement: [Ramsey Abbey, dioceseHistorically, Diocese of Lincoln]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseHistorically Context triple: [Ramsey Abbey, dioceseHistorically, Diocese of Lincoln]
-
A.
hasDioceseHistory
Indicates that an entity has an associated historical record or account of its diocese, including its past developments, changes, or events.
-
B.
governingDioceseHistorical
chosen
Indicates that one diocese historically exercised governing authority or jurisdiction over another ecclesiastical entity.
-
C.
isHistoricDiocese
Indicates that an entity functioned as a diocese in the past but no longer exists as an active ecclesiastical jurisdiction.
-
D.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
E.
diocese
Indicates that one entity serves as the ecclesiastical district or jurisdiction under the authority of a bishop to which the other entity is related or belongs.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab248748190858420c09bbdba32 |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.