Triple
T22879220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velabrum |
E567413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman district |
C32296
|
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: ancient Roman district Context triple: [Velabrum, instanceOf, ancient Roman district]
-
A.
ancient district
An ancient district is a historically defined administrative or geographic area that existed in antiquity, often characterized by distinct political, cultural, or social functions within a larger civilization.
-
B.
Roman town
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
-
C.
rione of Rome
chosen
A rione of Rome is a traditional administrative district within the historic center of the city, each with its own distinct history, identity, and urban character.
-
D.
area of ancient Rome
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.
-
E.
ancient Roman agora
An ancient Roman agora is a central public space in a Roman city used for markets, political gatherings, social interaction, and religious activities, typically surrounded by important civic and commercial buildings.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:39 p.m.