Triple
T34498935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Honorius |
E885694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman court |
C13469
|
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 court Context triple: [court of Honorius, instanceOf, late Roman court]
-
A.
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.
-
B.
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.
-
C.
Roman imperial household
chosen
The Roman imperial household comprised the emperor’s family, slaves, freedmen, and administrative staff who managed both the private affairs and many public functions of the imperial court.
-
D.
Roman legal academy
A Roman legal academy is an institution dedicated to the systematic study, teaching, and interpretation of Roman law, its principles, procedures, and historical development.
-
E.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.