Triple
T31266663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unterlinden convent |
E797271
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dominican religious complex |
C25345
|
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: Dominican religious complex Context triple: [Unterlinden convent, instanceOf, Dominican religious complex]
-
A.
Dominican church
A Dominican church is a Christian place of worship administered by the Order of Preachers (Dominicans), typically emphasizing preaching, education, and a relatively austere architectural style.
-
B.
Christian monastic complex
chosen
A Christian monastic complex is an integrated group of religious buildings and spaces—such as a church, cloister, dormitories, refectory, and work areas—designed to support the communal, spiritual, and daily life of monks or nuns.
-
C.
ancient monastic complex
An ancient monastic complex is a historically significant, self-contained religious settlement comprising monasteries, chapels, living quarters, and communal facilities where monastic communities lived, worshipped, and worked.
-
D.
Capuchin religious house
A Capuchin religious house is a monastic residence where members of the Capuchin branch of the Franciscan Order live in community, following a life of prayer, poverty, and service.
-
E.
Benedictine complex
A Benedictine complex is an architectural ensemble centered around a Benedictine monastery, typically including a church, cloister, living quarters, workspaces, and communal facilities arranged to support monastic life according to the Rule of Saint Benedict.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:13 p.m.