Triple
T15792595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year Zero |
E382895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical policy |
C36494
|
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: historical policy Context triple: [Year Zero, instanceOf, historical policy]
-
A.
historical political system
A historical political system is an organized structure of governance, power relations, and institutions that operated within a specific society and time period, shaping how authority was distributed, exercised, and justified.
-
B.
historical topic
A historical topic is a specific subject, event, period, or theme from the past that is studied, analyzed, and interpreted to understand historical developments and their impact.
-
C.
historical process
A historical process is a sequence of interconnected events and developments over time through which social, political, economic, or cultural conditions gradually change.
-
D.
historical sports policy
Historical sports policy is the study and framework of past rules, regulations, and governance decisions that shaped how sports were organized, played, and managed within specific social, political, and cultural contexts.
-
E.
historical polities
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
- F. None of above. chosen
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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.