Triple
T3816458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindisfarne |
E84266
|
entity |
| Predicate | monasteryDissolved |
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: [Lindisfarne, monasteryDissolved, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasteryDissolved Context triple: [Lindisfarne, monasteryDissolved, 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.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
C.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
D.
dissolvedAsPriory
Indicates that a religious house or priory ceased to exist or operate due to formal dissolution.
-
E.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7482d708190a3ec74745b102a4c |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.