Triple
T27541277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayuan |
E695241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic-influenced polity |
C37616
|
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: Hellenistic-influenced polity Context triple: [Dayuan, instanceOf, Hellenistic-influenced polity]
-
A.
Hellenistic-influenced culture
chosen
A Hellenistic-influenced culture is a society whose language, art, religion, politics, or social practices have been significantly shaped by the spread and adaptation of Greek traditions following Alexander the Great’s conquests.
-
B.
Hellenistic institution
A Hellenistic institution is an organized social, political, religious, or educational structure that developed or operated within the culturally blended Greek-influenced societies of the Hellenistic period (c. 323–31 BCE).
-
C.
Hellenistic-era kingdom
A Hellenistic-era kingdom is a monarchic state that emerged from the fragmentation of Alexander the Great’s empire, blending Greek political and cultural forms with local traditions across the Eastern Mediterranean and Near East.
-
D.
Hellenistic-era monarch
A Hellenistic-era monarch is a ruler who governed one of the successor kingdoms to Alexander the Great’s empire, blending Greek political and cultural traditions with local customs across a diverse, often expansive territory.
-
E.
Greco-Roman settlement
A Greco-Roman settlement is a community or town established or influenced by ancient Greek and Roman cultures, characterized by their architectural styles, urban planning, social structures, and economic activities.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:31 p.m.