Triple
T5523910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrgi |
E144877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Etruscan settlement |
C14376
|
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: Etruscan settlement Context triple: [Pyrgi, instanceOf, Etruscan settlement]
-
A.
Etruscan city
chosen
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.
Numidian settlement
A Numidian settlement is a community or town established by the ancient Numidian people of North Africa, typically characterized by fortified hilltop locations, mixed pastoral-agricultural economies, and cultural influences from both indigenous Berber traditions and Mediterranean civilizations.
-
C.
ancient Italic tribe
An ancient Italic tribe is a prehistoric or early historic ethnic group indigenous to the Italian Peninsula, characterized by its own language, culture, and social organization prior to Roman unification.
-
D.
Celtic settlement
A Celtic settlement is a community or habitation site established by Celtic peoples, typically characterized by fortified hilltops, roundhouses, and a material culture reflecting Celtic social, economic, and religious practices.
-
E.
Roman settlement
A Roman settlement is a community established under Roman rule, characterized by Roman architecture, infrastructure, administration, and cultural practices integrated with local traditions.
- 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:34 p.m.