Triple
T25018451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government House, Melbourne |
E626205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italianate building |
C49686
|
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: Italianate building Context triple: [Government House, Melbourne, instanceOf, Italianate building]
-
A.
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.
-
B.
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.
-
C.
Shingle Style building
A Shingle Style building is a late-19th-century American structure characterized by continuous wood shingle cladding, asymmetrical massing, complex rooflines, and an emphasis on informal, picturesque forms that blend with their surroundings.
-
D.
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.
-
E.
classical-style building
A classical-style building is a structure characterized by symmetry, proportion, and the use of traditional Greco-Roman elements such as columns, pediments, and decorative 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:06 a.m.