Triple
T14504030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Gaul |
E340217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman region |
C5440
|
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: late Roman region Context triple: [Eastern Gaul, instanceOf, late Roman region]
-
A.
Roman province
chosen
A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
-
B.
Eastern Roman Empire
The Eastern Roman Empire, also known as the Byzantine Empire, was the continuation of the Roman Empire in its eastern provinces, centered on Constantinople, that preserved Roman governance, law, and culture while developing a distinct Greek-speaking Christian civilization from late antiquity through the Middle Ages.
-
C.
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.
-
D.
core territory of the Roman Empire
The core territory of the Roman Empire comprises the Italian peninsula and the western-central Mediterranean heartlands that formed the political, economic, and cultural center of Roman power and administration.
-
E.
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.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:21 a.m.