Triple
T9487448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman military history |
E228797
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subfield of ancient history |
C4824
|
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: subfield of ancient history Context triple: [Roman military history, instanceOf, subfield of ancient history]
-
A.
subfield of history
chosen
A subfield of history is a specialized area of historical study that focuses on a particular theme, period, region, method, or group to provide more detailed and nuanced understanding of the past.
-
B.
history of the ancient world
The history of the ancient world examines the civilizations, cultures, events, and interactions of human societies from the earliest recorded times to the fall of the Western Roman Empire.
-
C.
historian of the ancient Near East
A historian of the ancient Near East is a scholar who researches, analyzes, and interprets the cultures, languages, politics, and societies of civilizations such as Mesopotamia, Egypt, the Levant, and Anatolia from prehistoric times through the early first millennium CE.
-
D.
field of archaeology
A field of archaeology is a specific area of study within archaeology that focuses on particular types of evidence, regions, time periods, methods, or theoretical approaches to understand past human cultures.
-
E.
ancient civilization
An ancient civilization is a complex, organized society from antiquity characterized by urban development, social stratification, specialized labor, centralized governance, and enduring cultural, technological, and architectural achievements.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:55 p.m.