Triple
T20492242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicomedeia |
E502773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Byzantine administrative center |
C6165
|
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 Byzantine administrative center Context triple: [Nicomedeia, instanceOf, former Byzantine administrative center]
-
A.
Byzantine city
chosen
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.
-
B.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
-
C.
Roman administrative headquarters
A Roman administrative headquarters is a central complex where imperial officials coordinated governance, taxation, legal affairs, and military logistics for a province or city.
-
D.
former capital city
A former capital city is an urban center that once served as the official seat of government and administrative authority for a country or region but no longer holds that status.
-
E.
Byzantine successor state
A Byzantine successor state is a political entity that emerged from the fragmentation of the Byzantine Empire, claiming continuity with its imperial, cultural, and religious traditions.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:35 a.m.