Triple
T31077581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regionary Catalogues of Rome |
E792007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman administrative list |
C45442
|
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 list Context triple: [Regionary Catalogues of Rome, instanceOf, Roman administrative list]
-
A.
Roman administrative text
chosen
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.
-
B.
Roman state formula
A Roman state formula is a standardized legal or ceremonial expression used in official Roman documents and rituals to articulate the authority, structure, and obligations of the Roman state.
-
C.
Roman official
A Roman official is a government functionary of ancient Rome responsible for administering laws, finances, justice, or public works within the Republic or Empire.
-
D.
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.
-
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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.