Triple
T11743270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Troy Book |
E279206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | retelling of the Trojan War |
C17303
|
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: retelling of the Trojan War Context triple: [The Troy Book, instanceOf, retelling of the Trojan War]
-
A.
retelling of the Mahabharata
A retelling of the Mahabharata is a reimagined narrative of the ancient Indian epic that preserves its core characters, events, and themes while adapting the story’s perspective, style, or context for a new audience.
-
B.
mythological war
A mythological war is a large-scale, often cosmic conflict between gods, heroes, and supernatural beings that explains or symbolizes fundamental cultural, moral, or natural forces within a mythic tradition.
-
C.
post-Homeric epic
chosen
A post-Homeric epic is a long narrative poem composed after and in conscious relation to the Homeric epics, typically expanding, reinterpreting, or supplementing episodes and characters from the Iliad and Odyssey within the same mythological tradition.
-
D.
character in the Iliad
A character in the Iliad is an individual—mortal or divine—who participates in, influences, or is affected by the events of the Trojan War as narrated in Homer’s epic.
-
E.
ancient Greek war
Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.