Triple
T26800856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan Buddhist chronicles |
E671095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical narrative genre |
C46391
|
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: historical narrative genre Context triple: [Tibetan Buddhist chronicles, instanceOf, historical narrative genre]
-
A.
work of narrative history
chosen
A work of narrative history is a factual account of past events told in a story-driven, literary style that emphasizes characters, chronology, and vivid detail while remaining grounded in historical evidence.
-
B.
didactic historical romance
A didactic historical romance is a love story set in a carefully rendered past era that explicitly aims to teach readers moral, social, or historical lessons through its characters’ romantic journeys.
-
C.
historical drama
A historical drama is a narrative work that portrays fictionalized or real characters and events set in a past era, emphasizing period-accurate settings, costumes, and social conditions to explore human experiences within their historical context.
-
D.
Latin narrative history
Latin narrative history is a genre of historical writing in Latin that presents past events in a continuous, story-like prose, often emphasizing character, causation, and moral or political interpretation.
-
E.
legendary narrative
A legendary narrative is a traditional story, often rooted in historical events or figures, that has been embellished over time with mythical or supernatural elements to convey cultural values or explain the extraordinary.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 4:22 a.m.