Triple
T32003929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman collegium |
E817210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman association |
C61272
|
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: ancient Roman association Context triple: [Roman collegium, instanceOf, ancient Roman association]
-
A.
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.
-
B.
area of ancient Rome
An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
-
C.
Roman concept
A Roman concept is an abstract idea, value, or practice rooted in the culture, politics, religion, or daily life of ancient Rome, such as virtus (virtue), pietas (duty), or imperium (authority).
-
D.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
E.
ancient Italo-Roman relations
Ancient Italo-Roman relations encompass the political, military, economic, and cultural interactions between Rome and the diverse Italic peoples of the Italian peninsula from early expansion through the Social War and the integration of Italy into the Roman state.
- F. None of above. chosen
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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:14 a.m.