Triple
T27964507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medeshamstede |
E704678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval monastic settlement |
C29712
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: early medieval monastic settlement Context triple: [Medeshamstede, instanceOf, early medieval monastic settlement]
-
A.
medieval monastic site
A medieval monastic site is a religious complex, typically enclosed and self-sufficient, where monks or nuns lived, worshipped, worked, and followed a regulated spiritual routine during the Middle Ages.
-
B.
early medieval site
chosen
An early medieval site is an archaeological location dating roughly from the 5th to the 11th century CE that preserves material evidence of social, political, economic, and religious life during the early Middle Ages.
-
C.
Romanesque monastery
A Romanesque monastery is a medieval monastic complex characterized by massive stone construction, rounded arches, barrel or groin vaults, and a cloister-centered layout designed for communal religious life, prayer, and self-sufficiency.
-
D.
Cistercian monastery
A Cistercian monastery is a self-contained religious community following the Cistercian Order’s strict observance of the Rule of St. Benedict, characterized by simplicity, manual labor, and communal prayer.
-
E.
former Benedictine monastery
A former Benedictine monastery is a religious complex once inhabited and operated by Benedictine monks, now no longer functioning as an active Benedictine community but often preserved or repurposed for other uses.
- F. None of above.
Provenance (1 batch)
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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 7:34 p.m.