Triple
T29572225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman engineering |
E753343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural heritage of ancient Rome |
C6303
|
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: cultural heritage of ancient Rome Context triple: [Roman engineering, instanceOf, cultural heritage of ancient Rome]
-
A.
area of ancient Rome
An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
-
B.
ancient Roman
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
-
C.
heritage of classical antiquity
chosen
The heritage of classical antiquity encompasses the enduring cultural, intellectual, artistic, and political legacies of ancient Greece and Rome that have profoundly shaped subsequent civilizations, especially in Europe and the Western world.
-
D.
ancient Roman literature
Ancient Roman literature encompasses the body of written works produced in Latin (and some Greek) by Roman authors, reflecting the political, social, philosophical, and artistic life of Rome from its early Republic through the Imperial period.
-
E.
roman
A Roman is a member or characteristic of the ancient civilization of Rome, encompassing its people, culture, architecture, governance, and influence on Western history.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 5:59 p.m.