Triple
T8312521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brundisium |
E194623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement in ancient Italy |
C24210
|
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: settlement in ancient Italy Context triple: [Brundisium, instanceOf, settlement in ancient Italy]
-
A.
Ligurian settlement
A Ligurian settlement is a historically or archaeologically identified inhabited place established or predominantly occupied by the ancient Ligurian people, characterized by their distinct cultural, social, and territorial attributes.
-
B.
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.
-
C.
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.
-
D.
oasis settlement
An oasis settlement is a community established around a natural water source in an otherwise arid or desert region, relying on the oasis for agriculture, trade, and habitation.
-
E.
settlement in Russia
A settlement in Russia is a populated locality, ranging from small rural communities to larger urban-type areas, officially recognized within the country’s administrative-territorial structure.
- F. None of above. chosen
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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.