Triple
T17672553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia (ancient city) |
E440558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | city of Lydia |
C39514
|
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: city of Lydia Context triple: [Philadelphia (ancient city), instanceOf, city of Lydia]
-
A.
Lycian city
A Lycian city is an ancient urban settlement located in the historical region of Lycia in southwestern Anatolia, characterized by its distinctive rock-cut tombs, fortified acropoleis, and integration of Greek, Persian, and indigenous Lycian cultural elements.
-
B.
ancient Lydian dynasty
The ancient Lydian dynasty refers to the line of kings who ruled the kingdom of Lydia in western Anatolia, most notably the Mermnad dynasty (c. 7th–6th centuries BCE), famed for its wealth, early coinage, and interactions with Greek and Persian powers.
-
C.
king of Lydia
A king of Lydia is the sovereign ruler of the ancient Anatolian kingdom of Lydia, holding supreme political, military, and religious authority over its people and territories.
-
D.
Phrygian city
A Phrygian city is an ancient urban settlement located in the historical region of Phrygia in central Anatolia, characterized by its distinctive rock-cut architecture, religious monuments, and role in the Phrygian kingdom’s political and cultural life.
-
E.
Lydian king
A Lydian king is the sovereign ruler of the ancient kingdom of Lydia, overseeing its political, military, economic, and religious affairs within the context of Anatolian and wider Near Eastern power dynamics.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10 a.m.