Triple
T18703251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Tripoli |
E457304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event of the Crusades |
C17123
|
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: event of the Crusades Context triple: [Siege of Tripoli, instanceOf, event of the Crusades]
-
A.
event in the Albigensian Crusade
An "event in the Albigensian Crusade" is a specific historical occurrence—such as a battle, siege, council, treaty, or massacre—that took place within the context and timeframe of the early 13th-century papal military campaign against the Cathars in southern France.
-
B.
Crusades battle
chosen
A Crusades battle is a large-scale medieval military engagement between Christian and Muslim forces (and their allies) fought primarily in the Eastern Mediterranean and surrounding regions as part of the religiously motivated campaigns known as the 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.