Triple
T9239893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persianate world |
E222032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civilizational zone |
C145
|
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: civilizational zone Context triple: [Persianate world, instanceOf, civilizational zone]
-
A.
cultural region
chosen
A cultural region is a geographic area characterized by shared cultural traits such as language, religion, customs, and social norms that distinguish it from surrounding areas.
-
B.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
C.
civilization classification scale
A civilization classification scale is a conceptual framework that categorizes civilizations based on measurable criteria such as their energy consumption, technological advancement, or ability to utilize and manipulate resources at planetary, stellar, or galactic scales.
-
D.
infrastructure development zone
An infrastructure development zone is a designated geographic area prioritized for the planning, investment, and construction of essential public facilities and services—such as transportation, utilities, and communications—to support economic growth and urban or regional development.
-
E.
traditional area
A traditional area is a geographically defined region recognized for its longstanding cultural, historical, or customary significance, often governed by inherited practices and community norms.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:30 p.m.