Triple
T9308631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio X Palatium |
E223952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regio of the city of Rome |
C12791
|
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: regio of the city of Rome Context triple: [Regio X Palatium, instanceOf, regio of the city of Rome]
-
A.
area of ancient Rome
chosen
An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
-
B.
cultural heritage monument in Rome
A cultural heritage monument in Rome is a historically or artistically significant structure or site within the city that embodies its ancient, medieval, Renaissance, or modern legacy and is protected for its cultural value.
-
C.
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.
-
D.
Roma subgroup
A Roma subgroup is a distinct community within the broader Romani people, defined by shared ancestry, dialect, cultural practices, and often historical migration patterns.
-
E.
Etruscan city
An Etruscan city is an urban center of the ancient Etruscan civilization in central Italy, characterized by fortified hilltop locations, planned street layouts, religious and civic monuments, and a strong regional trade and cultural network.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.