Triple
T20271274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalric, Prince of Tyre |
E499098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lusignan dynasty member |
C20316
|
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: Lusignan dynasty member Context triple: [Amalric, Prince of Tyre, instanceOf, Lusignan dynasty member]
-
A.
member of the House of Lusignan
chosen
A member of the House of Lusignan is an individual belonging to the medieval French noble dynasty that rose to prominence as lords of Lusignan and later as kings of Jerusalem, Cyprus, and Armenia.
-
B.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
C.
Luxembourg dynasty member
A Luxembourg dynasty member is an individual belonging to the medieval European royal House of Luxembourg, which produced several Holy Roman Emperors, kings, and high-ranking nobles.
-
D.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
E.
Ottonian dynasty member
An Ottonian dynasty member is an individual belonging to the German royal and imperial family that ruled the East Frankish (German) kingdom and Holy Roman Empire from the early 10th to early 11th centuries, beginning with Henry the Fowler and most prominently represented by Otto I, Otto II, and Otto III.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:42 p.m.