Triple
T29443325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smyrna (as legate or curator) |
E746777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman administrative office |
C17185
|
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: Roman administrative office Context triple: [Smyrna (as legate or curator), instanceOf, Roman administrative office]
-
A.
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.
-
B.
Roman administrative district
A Roman administrative district is a territorial unit governed by Roman officials for the purposes of taxation, legal jurisdiction, military organization, and local administration within the Roman state.
-
C.
Roman administrative text
A Roman administrative text is a written document produced by Roman authorities to record, regulate, or communicate matters of governance, such as laws, edicts, census data, tax records, and official correspondence.
-
D.
Roman cultural institution
A Roman cultural institution is an organized social, religious, political, or recreational structure—such as temples, forums, baths, theaters, or legal bodies—that shaped and reflected the values, practices, and public life of ancient Roman society.
-
E.
Roman official
chosen
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:24 p.m.