Triple
T6240206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanda Empire |
E139580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Indian empire |
C4987
|
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 Indian empire Context triple: [Nanda Empire, instanceOf, ancient Indian empire]
-
A.
ancient empire
chosen
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.
-
B.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
C.
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.
-
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.
Indus Valley Civilization site
An Indus Valley Civilization site is an archaeological location associated with the Bronze Age urban culture of the northwestern Indian subcontinent, characterized by planned cities, advanced drainage systems, and material remains reflecting complex social, economic, and religious life.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:23 p.m.