Triple
T13411186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noviomagus |
E320089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman place name |
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: ancient Roman place name Context triple: [Noviomagus, instanceOf, ancient Roman place name]
-
A.
Roman name
A Roman name is a personal designation used in ancient Rome, typically composed of multiple parts (such as praenomen, nomen, and cognomen) that indicated an individual's given name, family lineage, and sometimes personal traits or achievements.
-
B.
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.
-
C.
Latin toponym
A Latin toponym is a place name expressed in the Latin language, often used historically in maps, texts, and scholarly works to refer to geographic locations.
-
D.
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.
-
E.
ancient Roman structure
An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:35 p.m.