Triple
T912298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hart House |
E19687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gothic Revival architecture building |
C5890
|
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: Gothic Revival architecture building Context triple: [Hart House, instanceOf, Gothic Revival architecture building]
-
A.
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.
-
B.
Georgian church building
A Georgian church building is a Christian place of worship constructed or used during the Georgian era (1714–1830/37), typically characterized by balanced classical proportions, restrained ornamentation, and often brick or stone facades reflecting the architectural tastes of that period.
-
C.
stone church building
A stone church building is a religious structure constructed primarily from stone, typically featuring architectural elements such as a nave, altar, and often a steeple or tower for worship and community gatherings.
-
D.
Beaux-Arts building
A Beaux-Arts building is a grand, formally composed structure characterized by classical symmetry, rich ornamentation, and monumental scale, reflecting the academic architectural principles of the École des Beaux-Arts in Paris.
-
E.
fortified manor house
A fortified manor house is a residential estate that combines the domestic functions of a manor with defensive features such as walls, towers, and gatehouses to protect its inhabitants.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.