Triple
T23351386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibylla of Armenia |
E592920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Countess of Tripoli |
C47552
|
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: Countess of Tripoli Context triple: [Sibylla of Armenia, instanceOf, Countess of Tripoli]
-
A.
Countess of Sicily
The Countess of Sicily is a noblewoman holding the comital title associated with the island of Sicily, historically signifying high aristocratic rank, territorial authority, and dynastic influence within the Sicilian realm.
-
B.
Countess of Champagne
The Countess of Champagne is a noblewoman who holds the hereditary or marital title associated with ruling or representing the County of Champagne within the medieval French aristocracy.
-
C.
Countess of Anjou
The Countess of Anjou is a noblewoman who holds, by birth or marriage, the comital title associated with the medieval French county of Anjou, often playing significant political, dynastic, and social roles within European aristocracy.
-
D.
Princess of Antioch
A Princess of Antioch is a noblewoman of royal or princely rank associated with the medieval Principality of Antioch, typically by birth or marriage, who holds ceremonial status, dynastic significance, and potential political influence within the principality’s ruling house.
-
E.
Countess of Tyrol
A Countess of Tyrol is a noblewoman who holds the hereditary title and associated territorial authority over the historical region of Tyrol in the Alpine area of Central Europe.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:20 p.m.