Triple
T20650189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Familistère de Guise |
E507469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century architectural complex |
C16417
|
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: 19th-century architectural complex Context triple: [Familistère de Guise, instanceOf, 19th-century architectural complex]
-
A.
19th-century architectural project
A 19th-century architectural project is a planned building or complex designed and developed during the 1800s, reflecting the period’s characteristic styles, technologies, and cultural influences.
-
B.
19th-century residence
A 19th-century residence is a dwelling built or styled in the architectural traditions of the 1800s, typically featuring period-specific materials, ornamentation, and spatial layouts reflective of the social and technological context of that era.
-
C.
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.
-
D.
18th-century architectural project
An 18th-century architectural project is a designed building or complex conceived and planned during the 1700s, reflecting the period’s prevailing styles, construction techniques, and cultural or political ideals.
-
E.
civic building complex
chosen
A civic building complex is a coordinated group of public structures and spaces designed to house governmental, administrative, and community services within a unified physical setting.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.