Triple
T26383660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakatsumaki |
E663213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of a historical chronicle |
C43537
|
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: section of a historical chronicle Context triple: [Nakatsumaki, instanceOf, section of a historical chronicle]
-
A.
section of historical work
chosen
A section of historical work is a distinct, thematically organized subdivision of a larger historical text that presents and analyzes specific events, periods, or topics within the broader narrative.
-
B.
collection of chronicles
A collection of chronicles is an organized compilation of narrative records, each detailing events or experiences over time, often grouped by theme, period, or source.
-
C.
work of narrative history
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.
-
D.
verse chronicle
A verse chronicle is a historical or narrative account of real or legendary events told in the form of poetry, often arranged in chronological order.
-
E.
12th-century chronicle
A 12th-century chronicle is a medieval historical narrative, typically written by a monk or cleric, that records events of its time in roughly chronological order, blending factual reporting with religious interpretation and local tradition.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:20 p.m.