Triple
T14456729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annales Laureshamenses |
E358477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Latin annals |
C34795
|
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 Latin annals Context triple: [Annales Laureshamenses, instanceOf, medieval Latin annals]
-
A.
royal annals
Royal annals are chronological records maintained by or for a monarchy that document significant political, military, religious, and ceremonial events of a ruler’s reign.
-
B.
Anglo-Norman manuscript tradition
The Anglo-Norman manuscript tradition encompasses the body of texts written in Anglo-Norman French in medieval England, preserved and transmitted through manuscripts that reflect the linguistic, cultural, and political interplay between Norman and English societies from the 11th to the 15th centuries.
-
C.
medieval commentary
A medieval commentary is a scholarly work from the Middle Ages that explains, interprets, and elaborates on an authoritative text, often blending exposition with theological, philosophical, or legal analysis.
-
D.
medieval Latin script
Medieval Latin script is a broad category of handwritten Latin letterforms used in Europe from late antiquity through the late Middle Ages, encompassing diverse regional and functional styles such as Carolingian minuscule, Gothic script, and various cursive hands.
-
E.
Byzantine chronicle
A Byzantine chronicle is a historical narrative, often arranged annalistically, that records events of the Byzantine Empire and surrounding regions, typically blending factual reporting with religious interpretation and classical traditions.
- F. None of above. chosen
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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.