Triple
T22944920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruritanian romance |
E569838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | adventure fiction subgenre |
C5785
|
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: adventure fiction subgenre Context triple: [Ruritanian romance, instanceOf, adventure fiction subgenre]
-
A.
adventure book
An adventure book is a narrative work that follows characters through exciting, often perilous journeys filled with action, exploration, and unexpected challenges.
-
B.
historical adventure fiction
chosen
Historical adventure fiction is a genre that blends meticulously researched past settings and events with fast-paced, often perilous journeys or quests, emphasizing action, exploration, and personal heroism within a specific historical context.
-
C.
subgenre of action-adventure games
A subgenre of action-adventure games is a more narrowly defined category within the broader action-adventure genre that emphasizes specific gameplay mechanics, themes, or narrative structures, such as stealth-focused play, open-world exploration, or survival elements.
-
D.
adventure series
An adventure series is a sequence of related stories or episodes that follow characters through exciting, often perilous journeys filled with exploration, challenges, and discoveries.
-
E.
sea adventure novel
A sea adventure novel is a narrative centered on perilous voyages, maritime exploration, and high-stakes conflicts on or beneath the ocean, often highlighting human resilience against the unpredictable power of the sea.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:45 p.m.