Triple
T3462437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campus Martius |
E73056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | area of ancient Rome |
C12791
|
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: area of ancient Rome Context triple: [Campus Martius, instanceOf, area of ancient Rome]
-
A.
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.
-
B.
ancient empire
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
C.
phase of the Roman Empire
A phase of the Roman Empire is a distinct historical period characterized by specific political structures, territorial extents, social dynamics, and cultural developments within the broader continuum of Roman rule.
-
D.
ancient country
An ancient country is a historically significant territorial and political entity that existed in antiquity, characterized by its own culture, governance, and defined geographic boundaries.
-
E.
Roman town
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.