Triple
T11627851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherborne Abbey |
E276318
|
entity |
| Predicate | monasteryDissolvedIn |
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: [Sherborne Abbey, monasteryDissolvedIn, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasteryDissolvedIn Context triple: [Sherborne Abbey, monasteryDissolvedIn, 16th century]
-
A.
dissolvedAsMonastery
chosen
Indicates that an institution ceased to function as a monastery, typically through formal dissolution or suppression of its monastic status.
-
B.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
C.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
D.
abbeyDissolvedDuring
Indicates that an abbey ceased to exist or was formally disbanded during a specified time period or event.
-
E.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a1259cd08190a75eeacb5e39b858 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.