Triple
T34554409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Part of the General estoria |
E887162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval historical chronicle section |
C43626
|
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: medieval historical chronicle section Context triple: [Third Part of the General estoria, instanceOf, medieval historical chronicle section]
-
A.
12th-century chronicle
chosen
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.
-
B.
medieval era
The medieval era is a historical period roughly spanning the 5th to the 15th century in Europe, characterized by feudal societies, the dominance of the Catholic Church, and the gradual emergence of towns, universities, and nation-states.
-
C.
medievalist
A medievalist is a scholar or enthusiast who studies and interprets the history, culture, literature, and societies of the Middle Ages.
-
D.
medieval historical phenomenon
A medieval historical phenomenon is a significant social, political, economic, cultural, or religious development that emerged or transformed societies during the Middle Ages, typically between the 5th and 15th centuries.
-
E.
medieval event
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.