Triple
T20787872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Mary’s Church (Marienkirche) |
E511688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval architectural monument |
C27128
|
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: medieval architectural monument Context triple: [St. Mary’s Church (Marienkirche), instanceOf, medieval architectural monument]
-
A.
medieval architecture monument
chosen
A medieval architecture monument is a historically significant structure from the Middle Ages that exemplifies characteristic building styles, materials, and decorative elements of its period and culture.
-
B.
Manueline architectural monument
A Manueline architectural monument is a grand structure exemplifying the ornate, late-Gothic Portuguese style characterized by intricate maritime, religious, and royal symbolism carved into stone.
-
C.
medieval castle
A medieval castle is a fortified stone stronghold featuring defensive walls, towers, and a keep, designed to protect its inhabitants and assert the power of its lord.
-
D.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
E.
medieval architectural style
A medieval architectural style is a historically rooted design tradition characterized by features such as thick stone walls, arches, vaults, and ornamental detailing that reflect the cultural, religious, and technological contexts of the Middle Ages.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:38 p.m.