Triple
T7237780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstelhof |
E155274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century building |
C19192
|
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: 17th-century building Context triple: [Amstelhof, instanceOf, 17th-century building]
-
A.
18th-century building
An 18th-century building is a structure constructed between 1701 and 1800 that typically reflects the architectural styles, materials, and construction techniques of that period, such as Georgian, Baroque, or Neoclassical design.
-
B.
17th-century church
A 17th-century church is a religious building constructed in the 1600s that typically reflects Baroque or late Renaissance architectural styles, serving as a place of Christian worship and community gathering.
-
C.
Baroque building
chosen
A Baroque building is an architecturally elaborate structure characterized by dramatic forms, rich ornamentation, dynamic curves, and a strong emphasis on grandeur and theatrical visual effects.
-
D.
Renaissance building
A Renaissance building is a structure characterized by symmetry, proportion, and classical elements such as columns, pilasters, arches, and domes, reflecting the revival of ancient Greek and Roman architectural principles during the 14th–17th centuries.
-
E.
18th-century residence
An 18th-century residence is a dwelling built or styled in the architectural traditions of the 1700s, typically featuring symmetrical facades, period-appropriate materials, and interior layouts reflecting the social and domestic norms of the era.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:55 p.m.