Triple
T17699301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Oultrejordain |
E441253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Crusader lordship |
C6121
|
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 lordship Context triple: [Lordship of Oultrejordain, instanceOf, Crusader lordship]
-
A.
Crusader state
chosen
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
-
B.
King of Jerusalem
The King of Jerusalem was the monarch who ruled the Crusader-founded Kingdom of Jerusalem, a Christian realm established in the Levant after the First Crusade.
-
C.
King of Jerusalem
The King of Jerusalem is the sovereign ruler of the medieval Crusader Kingdom of Jerusalem, holding both political authority and symbolic religious significance over the Holy City and its surrounding territories.
-
D.
participants in the Crusades
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.
-
E.
Prince of Achaea
A Prince of Achaea is a noble ruler or heir of the ancient Greek region of Achaea, responsible for governing its territories, leading its warriors, and upholding its political and cultural traditions.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:04 a.m.