Triple
T15002008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin Crusaders |
E374113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Crusader army |
C16873
|
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: Crusader army Context triple: [Latin Crusaders, instanceOf, Crusader army]
-
A.
Guards field army
The Guards field army is an elite, front-line military formation composed of highly trained and well-equipped units tasked with executing critical offensive and defensive operations on behalf of a state or empire.
-
B.
Parliamentarian cavalry
Parliamentarian cavalry were mounted troops loyal to the English Parliament during the Civil War, combining mobility, shock tactics, and disciplined formations to challenge Royalist forces on the battlefield.
-
C.
Parliamentarian army
A Parliamentarian army is a military force organized, funded, and directed by a parliamentary body to wage war or maintain order in support of its political authority and policies.
-
D.
Count of Tripoli
A Count of Tripoli is a noble title historically associated with the ruler or feudal lord governing the County of Tripoli, a Crusader state established in the Levant during the Middle Ages.
-
E.
participants in the Crusades
chosen
Participants in the Crusades were diverse groups of medieval Christian, Muslim, and occasionally Jewish or other regional actors—including knights, soldiers, rulers, clergy, merchants, and peasants—who engaged in or were directly affected by a series of religiously framed military campaigns between the 11th and 15th centuries.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:54 a.m.