Triple
T27168473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bordesley Abbey ruins |
E682839
|
entity |
| Predicate | disestablishedAsMonastery |
P27496
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Bordesley Abbey ruins, disestablishedAsMonastery, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disestablishedAsMonastery Context triple: [Bordesley Abbey ruins, disestablishedAsMonastery, 16th century]
-
A.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
B.
stillInUseAsMonastery
Indicates that a building or site continues to function as a monastery in the present time.
-
C.
dissolvedAsMonastery
chosen
Indicates that an institution ceased to function as a monastery, typically through formal dissolution or suppression of its monastic status.
-
D.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
E.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625451be88190b9b2c24b3d50e09c |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:22 a.m.