Triple

T23649762
Position Surface form Disambiguated ID Type / Status
Subject Augustodunum – Autun E584135 entity
Predicate instanceOf P0 FINISHED
Object former Roman city C5442 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: former Roman city
Context triple: [Augustodunum – Autun, instanceOf, former Roman city]
  • A. Roman town chosen
    A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
  • B. Byzantine city
    A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
  • C. Etruscan city
    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.
  • D. 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.
  • E. ancient ruined city
    An ancient ruined city is a long-abandoned urban settlement whose remaining structures, artifacts, and landscape features reveal the remnants of a once-thriving civilization now decayed by time and nature.
  • 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_69e248fefafc81909656921192f30e80 completed April 17, 2026, 2:51 p.m.
Created at: April 17, 2026, 6:49 p.m.