Triple
T8697905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rushen Abbey |
E206446
|
entity |
| Predicate | convertedToCistercianOrder |
P62813
|
FINISHED |
| Object | 1147 |
—
|
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: 1147 | Statement: [Rushen Abbey, convertedToCistercianOrder, 1147]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToCistercianOrder Context triple: [Rushen Abbey, convertedToCistercianOrder, 1147]
-
A.
convertedToCistercian
chosen
Indicates that an entity has changed its religious affiliation or institutional status to become part of the Cistercian order.
-
B.
convertedToChurch
Indicates that something has been transformed or repurposed into a church.
-
C.
refoundedAsBenedictineMonastery
Indicates that something was re-established or reorganized specifically as a Benedictine monastery.
-
D.
originallyCatholicOrder
Indicates that an organization or group was initially founded as a Catholic religious order, regardless of its later status or affiliation.
-
E.
sisterMonastery
Indicates a formal sister-monastery relationship between two monastic institutions, typically involving mutual support, affiliation, or shared spiritual ties.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58af50408190a3b81100a759795e |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.