Triple
T13937240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historia Brittonum |
E335150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval historical text |
C1507
|
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 text Context triple: [Historia Brittonum, instanceOf, medieval historical text]
-
A.
medieval prose text
chosen
A medieval prose text is a written work from the Middle Ages composed in continuous, non-verse form, often preserving narratives, religious teachings, legal codes, or historical accounts in the vernacular or Latin.
-
B.
medievalist
A medievalist is a scholar or enthusiast who studies and interprets the history, culture, literature, and societies of the Middle Ages.
-
C.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
-
D.
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.
-
E.
early medieval Christian text
An early medieval Christian text is a written work produced roughly between the 5th and 11th centuries that reflects and shapes Christian theology, liturgy, devotion, or ecclesiastical practice within the cultural and political contexts of early medieval Europe and the Mediterranean.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:17 p.m.