Triple
T35073208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahab versus Moby Dick |
E1011938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | literary conflict |
C11375
|
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: literary conflict Context triple: [Ahab versus Moby Dick, instanceOf, literary conflict]
-
A.
conflictInLiterature
chosen
conflictInLiterature is a conceptual class representing the central struggle between opposing forces—such as characters, ideas, or external circumstances—that drives the plot and reveals themes within a literary work.
-
B.
literary feud
A literary feud is an ongoing, often public conflict between writers, critics, or literary circles, typically expressed through works, reviews, letters, or commentary that critique or undermine one another’s ideas, style, or reputation.
-
C.
cinematic conflict archetype
A cinematic conflict archetype is a recurring, recognizable pattern of opposition between characters, forces, or ideals that structures a film’s drama and drives its narrative tension.
-
D.
cultural conflict
Cultural conflict is a clash between groups with differing values, beliefs, norms, or practices that leads to tension, misunderstanding, or struggle over identity, power, or resources.
-
E.
literaryWork
A literaryWork is a created written or spoken artistic composition, such as a novel, poem, or play, that conveys ideas, stories, or emotions through language.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.