Triple
T16665024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strada Felice |
E404961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance urban thoroughfare |
C27950
|
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: Renaissance urban thoroughfare Context triple: [Strada Felice, instanceOf, Renaissance urban thoroughfare]
-
A.
Renaissance square
A Renaissance square is a public urban space characterized by harmonious proportions, classical architectural elements, and a central role in civic, commercial, and cultural life during the Renaissance period.
-
B.
ancient Roman street
An ancient Roman street is a paved public thoroughfare, typically constructed of stone blocks with raised sidewalks, drainage systems, and often lined with shops, houses, and public buildings, facilitating movement, trade, and social interaction within Roman cities.
-
C.
east–west thoroughfare
An east–west thoroughfare is a primary transportation route or street that runs predominantly in an east–west direction, facilitating significant cross-town or regional movement.
-
D.
Renaissance town
A Renaissance town is an urban settlement characterized by humanist-inspired planning, harmonious proportions, and architecture that blends classical forms with emerging civic, commercial, and cultural functions of the 14th–17th centuries.
-
E.
civic thoroughfare
chosen
A civic thoroughfare is a major public street or corridor designed to accommodate high volumes of movement while structuring and showcasing key civic, cultural, and institutional functions of a community.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:18 a.m.