Triple
T6656390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycaonia |
E150956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient region of Asia Minor |
C7005
|
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 region of Asia Minor Context triple: [Lycaonia, instanceOf, ancient region of Asia Minor]
-
A.
region of Turkey
chosen
A region of Turkey is a large geographic and cultural area within the country, typically defined for administrative, economic, or historical purposes and encompassing multiple provinces, cities, and distinct local characteristics.
-
B.
region of the Mediterranean Sea
A region of the Mediterranean Sea is a geographically defined marine area within the Mediterranean basin, characterized by shared environmental conditions, maritime boundaries, and cultural or economic significance.
-
C.
region of Egypt
A region of Egypt is a geographically defined area within the country characterized by shared physical, cultural, economic, or administrative features that distinguish it from other parts of Egypt.
-
D.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
-
E.
historical region of Italy
A historical region of Italy is a geographically defined area that played a distinct political, cultural, or administrative role in Italy’s past, often predating or differing from the country’s modern regional boundaries.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:01 p.m.