Triple
T15289737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of Ulster |
E365495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Irish chronicle |
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 Irish chronicle Context triple: [Annals of Ulster, instanceOf, medieval Irish chronicle]
-
A.
Welsh chronicle
A Welsh chronicle is a historical narrative or annalistic record, written in or about Wales, that documents events, rulers, and significant occurrences in Welsh history over a period of time.
-
B.
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.
-
C.
medieval Latin annals
chosen
Medieval Latin annals are chronological, year-by-year historical records written in Latin during the Middle Ages, typically noting significant political, religious, and natural events in brief entries.
-
D.
monastic chronicle
A monastic chronicle is a historical narrative compiled and maintained by monks within a religious community, recording significant events, religious observances, and local or wider affairs over time.
-
E.
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.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.