Triple
T156871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titanomachy |
E3199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Greek mythology |
C1818
|
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 Greek mythology Context triple: [Titanomachy, instanceOf, event in Greek mythology]
-
A.
figure in Greek mythology
A figure in Greek mythology is a character—divine, heroic, or monstrous—who appears in the traditional myths of ancient Greece and embodies cultural values, natural forces, or moral lessons.
-
B.
event in the War of 1812
An "event in the War of 1812" is a specific historical occurrence—such as a battle, treaty, political decision, or military campaign—that took place between 1812 and 1815 and directly relates to the conflict between the United States, the United Kingdom, and their respective allies.
-
C.
event in the Vietnam War
An event in the Vietnam War is a specific, temporally bounded occurrence—such as a battle, operation, political decision, or diplomatic action—that significantly influenced the course, conduct, or consequences of the conflict.
-
D.
era in United States history
An era in United States history is a distinct time period characterized by particular political, social, economic, and cultural conditions or transformative events that differentiate it from other periods.
-
E.
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.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.