Triple
T25020876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notitia Dignitatum |
E626565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial document |
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 imperial document Context triple: [Notitia Dignitatum, instanceOf, Roman imperial document]
-
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.
late Roman legal codex
A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
-
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.
cuneiform document
A cuneiform document is a written artifact, typically on clay or stone, bearing information recorded in the wedge-shaped cuneiform script used by ancient Near Eastern civilizations.
-
E.
Vetus Latina manuscript
A Vetus Latina manuscript is a handwritten document preserving an Old Latin (pre-Vulgate) translation of biblical texts used in the Western Church before Jerome’s standardized Vulgate.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:06 a.m.