Triple
T5435230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cultural Revolution in Iran |
E121991
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Iran |
C1824
|
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: event in Iran Context triple: [Cultural Revolution in Iran, instanceOf, event in Iran]
-
A.
region of Iran
A region of Iran is a geographically and culturally distinct area within the country, often defined by shared historical, ethnic, linguistic, economic, or environmental characteristics.
-
B.
event
chosen
An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
-
C.
event in the War in Afghanistan (2001–2021)
An event in the War in Afghanistan (2001–2021) is a specific, temporally and geographically bounded occurrence—such as a battle, operation, attack, negotiation, or political decision—that significantly influenced the course, conduct, or consequences of the conflict.
-
D.
province of Iran
A province of Iran is a primary administrative division of the country, governed by a centrally appointed governor and encompassing multiple counties, cities, and rural districts.
-
E.
military event
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.