Triple
T30482652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signia |
E775626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Latin city |
C5442
|
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 Latin city Context triple: [Signia, instanceOf, ancient Latin city]
-
A.
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.
-
B.
Roman town
chosen
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.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
D.
Punic city
A Punic city is an urban settlement established or influenced by the Phoenician-Carthaginian civilization, characterized by its maritime trade orientation, fortified harbors, and distinctive blend of Semitic and local cultural elements.
-
E.
ancient port city
An ancient port city is a historical urban center located on a coast or navigable waterway that served as a hub for maritime trade, cultural exchange, and strategic defense.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:13 p.m.