Triple
T4611580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caravanserai |
E100569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Historical building type |
C16081
|
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: Historical building type Context triple: [Caravanserai, instanceOf, Historical building type]
-
A.
Romanesque Revival building
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.
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.
-
C.
Renaissance architecture building
A Renaissance architecture building is a structure characterized by symmetry, proportion, and the revival of classical Greco-Roman elements such as columns, pilasters, domes, and rounded arches, often adorned with harmonious decorative details.
-
D.
historic commercial building
A historic commercial building is a long-standing structure originally designed and used for business or trade that holds architectural, cultural, or historical significance.
-
E.
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.
- F. None of above. chosen
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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:12 p.m.