Triple
T25681704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica di San Giovanni dei Fiorentini (design proposals) |
E643956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural design competition |
C14134
|
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: architectural design competition Context triple: [Basilica di San Giovanni dei Fiorentini (design proposals), instanceOf, architectural design competition]
-
A.
architectural competition
chosen
An architectural competition is a formal process in which architects submit design proposals in response to a defined brief, with entries evaluated to select a winning scheme for potential commissioning.
-
B.
design competition
A design competition is an organized event where individuals or teams submit creative design solutions to a defined brief, which are then evaluated and ranked by judges based on specified criteria.
-
C.
architecture and design award
An architecture and design award is a formal recognition given to outstanding projects, professionals, or innovations that exemplify excellence, creativity, and impact in the fields of architecture and design.
-
D.
architectural design
Architectural design is the conceptual and creative process of planning, organizing, and detailing the form, function, and aesthetics of built environments and structures.
-
E.
architectural congress
An architectural congress is a formal gathering of architects, planners, scholars, and related professionals convened to discuss, present, and debate ideas, projects, and policies shaping the built environment.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:01 p.m.