Triple
T33083565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Nablus |
E846570
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title of the Crusader states |
C59530
|
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: title of the Crusader states Context triple: [Lord of Nablus, instanceOf, title of the Crusader states]
-
A.
Crusader state
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.
title of the Habsburg Netherlands
The title of the Habsburg Netherlands denotes the formal sovereign designation held by the Habsburg rulers (primarily as Dukes, Counts, and Lords of various Low Countries territories) over the composite polity of the Netherlands under their dynastic control from the early 16th to the late 18th century.
-
E.
Lord of Lusignan
The Lord of Lusignan is a feudal noble who holds dominion over the Lusignan estate, exercising military, judicial, and administrative authority within his lands under the broader hierarchy of medieval nobility.
- F. None of above. chosen
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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.