Triple
T12619705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attaleia |
E301347
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement in Pamphylia |
C32241
|
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 Pamphylia Context triple: [Attaleia, instanceOf, settlement in Pamphylia]
-
A.
settlement in ancient Italy
A settlement in ancient Italy is a populated place such as a village, town, or city that existed on the Italian peninsula during antiquity, characterized by its social organization, infrastructure, and interaction with surrounding communities and cultures.
-
B.
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.
-
C.
settlement in Scotland
A settlement in Scotland is any inhabited place, ranging from small hamlets and villages to towns and cities, recognized as a distinct community within the country’s geographic and administrative landscape.
-
D.
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.
-
E.
Roman–Pontic war
The Roman–Pontic war was a series of military conflicts between the Roman Republic and the Kingdom of Pontus, primarily under King Mithridates VI, over control of Asia Minor and the eastern Mediterranean in the 1st century BCE.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:13 p.m.