Triple
T22826045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duel of the Horatii and Curiatii |
E565661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | episode in Roman legend |
C13466
|
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: episode in Roman legend Context triple: [Duel of the Horatii and Curiatii, instanceOf, episode in Roman legend]
-
A.
Roman legendary characters
Roman legendary characters are mythic or semi-mythic figures from Rome’s foundational and heroic traditions whose stories blend history, folklore, and moral exempla to express Roman values and identity.
-
B.
episode of the Roman civil wars
An episode of the Roman civil wars is a distinct, temporally bounded conflict event or campaign involving Roman factions whose actions and outcomes contribute to the broader course of the civil wars.
-
C.
Trojan War episode
A Trojan War episode is a narrative unit within the larger mythic cycle of the Trojan War that focuses on a specific event, conflict, or interaction involving its characters and themes.
-
D.
event in ancient Rome
chosen
An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
-
E.
European legend
A European legend is a traditional narrative rooted in the history, folklore, and cultural imagination of European peoples, often blending real events or places with mythical, supernatural, or moral elements.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:34 p.m.