Triple
T18006314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historia Hierosolymitana |
E430757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | First Crusade chronicle |
C32587
|
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: First Crusade chronicle Context triple: [Historia Hierosolymitana, instanceOf, First Crusade chronicle]
-
A.
First Crusade narrative
A First Crusade narrative is a historical or fictional account that chronicles the events, motivations, experiences, and consequences of the late 11th-century Christian military expedition to the Holy Land.
-
B.
Crusade chronicle
chosen
A Crusade chronicle is a historical narrative or account that records events, experiences, and perspectives related to one or more of the medieval Crusades.
-
C.
engagement of the First Crusade
The engagement of the First Crusade is a military-historical event class encompassing the individual battles, sieges, skirmishes, and armed encounters involving crusader and opposing forces during the First Crusade (1096–1099).
-
D.
phase of the First Crusade
A phase of the First Crusade is a distinct chronological and thematic stage in the campaign, marked by specific military operations, leadership dynamics, geographic focus, and strategic or religious objectives.
-
E.
battle of the First Crusade
A battle of the First Crusade is a military engagement fought between crusader and opposing forces during the 1096–1099 campaign to capture the Holy Land, typically involving complex alliances, religious motivations, and shifting control of key territories.
- 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.