Triple
T3024049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-text |
E82533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | manuscript tradition |
C5642
|
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: manuscript tradition Context triple: [A-text, instanceOf, manuscript tradition]
-
A.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
B.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
C.
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.
-
D.
manuscript
chosen
A manuscript is a written or typed document, often in draft or original form, that records a work such as a book, article, or composition prior to formal publication or reproduction.
-
E.
historiographical tradition
A historiographical tradition is a coherent, historically developed approach to interpreting and writing about the past, characterized by shared methods, assumptions, and narrative patterns among historians.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.