Triple
T18006313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historia Hierosolymitana |
E430757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin prose chronicle |
C13616
|
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: Latin prose chronicle Context triple: [Historia Hierosolymitana, instanceOf, Latin prose chronicle]
-
A.
Latin prose biography
A Latin prose biography is a narrative work written in Latin that recounts and interprets the life, character, and deeds of an individual in continuous prose form.
-
B.
Latin prose
chosen
Latin prose is a form of written Latin characterized by continuous, non-metrical language used for narrative, rhetorical, historical, philosophical, legal, and everyday texts in ancient Rome and later Latin traditions.
-
C.
late antique historiographical work
A late antique historiographical work is a narrative or analytical text composed between roughly the third and eighth centuries CE that interprets past events, often blending classical historical methods with emerging religious, political, and cultural perspectives of the period.
-
D.
late antique historiographical work
A late antique historiographical work is a narrative text composed between the third and eighth centuries CE that interprets past events—often blending classical, Christian, and local traditions—to construct meaning, identity, and authority for its contemporary audience.
-
E.
ancient Greek prose work
An ancient Greek prose work is a written composition in the Greek language from antiquity, typically in continuous, non-metrical form, encompassing genres such as history, philosophy, rhetoric, and narrative.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:24 a.m.