Triple
T21621025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fore Abbey |
E533576
|
entity |
| Predicate | refoundedAsBenedictinePriory |
P11203
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Fore Abbey, refoundedAsBenedictinePriory, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refoundedAsBenedictinePriory Context triple: [Fore Abbey, refoundedAsBenedictinePriory, 13th century]
-
A.
refoundedAsBenedictineMonastery
chosen
Indicates that something was re-established or reorganized specifically as a Benedictine monastery.
-
B.
foundedAsConventFor
Indicates that an institution or building was originally established specifically to serve as a convent for a particular religious community or group.
-
C.
formerCistercianAbbey
Indicates that something was once a Cistercian abbey but no longer holds that status.
-
D.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
E.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bafef548190b3856bfad1ebdc0b |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.