Triple
T27357815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ætheling |
E685734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old English title |
C40611
|
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: Old English title Context triple: [Ætheling, instanceOf, Old English title]
-
A.
medieval English name
A medieval English name is a personal name used in England roughly between the 5th and 15th centuries, often reflecting Old English, Norman, or Latin influences and frequently tied to religious, occupational, or locational origins.
-
B.
Old English manuscript
An Old English manuscript is a handwritten document from early medieval England, typically on parchment, preserving texts in the Old English language along with their contemporary script, ornamentation, and material features.
-
C.
Old English religious text
An Old English religious text is a written work composed in the Old English language that conveys Christian doctrines, biblical narratives, liturgical materials, or moral teachings for spiritual instruction and devotion in early medieval England.
-
D.
Old English literary work
An Old English literary work is a written composition created in the Old English language (c. 5th–11th centuries), encompassing genres such as poetry, prose, and religious or historical texts that reflect the culture and society of early medieval England.
-
E.
Old English term
chosen
An Old English term is a word or expression originating from the early medieval English language (circa 5th–11th centuries), often preserved in historical texts and studied for its linguistic and cultural significance.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:52 a.m.