Triple
T9188473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | acropolis |
E220518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | topographical feature of ancient cities |
C25788
|
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: topographical feature of ancient cities Context triple: [acropolis, instanceOf, topographical feature of ancient cities]
-
A.
legendary city
A legendary city is a mythical or semi-mythical urban center, often described in folklore or ancient texts, renowned for its extraordinary wealth, advanced culture, or mysterious disappearance.
-
B.
topographical model
A topographical model is a conceptual representation that maps the spatial features and relationships of a terrain or surface, often including elevation, contours, and physical landmarks.
-
C.
ancient rock-hewn cave city
An ancient rock-hewn cave city is a sprawling settlement carved directly into cliffs or mountainsides, featuring interconnected dwellings, temples, and passageways sculpted from living stone.
-
D.
geoglyphs
Geoglyphs are large-scale designs or motifs created on the ground, typically by arranging or removing natural materials, so they are best viewed from an elevated perspective.
-
E.
ancient Chinese city
An ancient Chinese city is a fortified urban center that served as a political, economic, military, and cultural hub, characterized by planned layouts, defensive walls, gates, palaces, temples, markets, and residential quarters reflecting traditional Chinese cosmology and social hierarchy.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:24 p.m.