Triple
T4987470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ames Free Library |
E112038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque Revival library |
C10197
|
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: Romanesque Revival library Context triple: [Ames Free Library, instanceOf, Romanesque Revival library]
-
A.
Romanesque Revival building
chosen
A Romanesque Revival building is a structure designed in a 19th-century historicist style that reinterprets medieval Romanesque architecture through features like round arches, heavy masonry, robust towers, and deeply recessed openings.
-
B.
Baroque library
A Baroque library is an opulent, architecturally elaborate repository of books characterized by dramatic ornamentation, grand spatial compositions, and richly decorated interiors that reflect the Baroque era’s fusion of knowledge, art, and power.
-
C.
Greek Revival building
A Greek Revival building is a structure designed in the early- to mid-19th-century architectural style that emulates classical Greek temples through features like tall columns, pediments, symmetrical facades, and bold, simple moldings.
-
D.
Mediterranean Revival building
A Mediterranean Revival building is an architectural structure characterized by stucco walls, red tile roofs, arches, and ornamental details inspired by Spanish, Italian, and other Mediterranean coastal traditions.
-
E.
Gothic Revival church
A Gothic Revival church is a Christian worship building designed in the 19th-century revival of medieval Gothic architecture, featuring pointed arches, ribbed vaults, and ornate tracery.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:34 p.m.