Triple
T33624338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dilshad Khatun |
E861359
|
entity |
| Predicate | monarchOfConsortTo |
P9813
|
FINISHED |
| Object | Abu Saʿid Bahadur Khan |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Abu Saʿid Bahadur Khan | Statement: [Dilshad Khatun, monarchOfConsortTo, Abu Saʿid Bahadur Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchOfConsortTo Context triple: [Dilshad Khatun, monarchOfConsortTo, Abu Saʿid Bahadur Khan]
-
A.
monarchOfConsort
Indicates that one entity is the consort (spouse) of the reigning monarch of another entity (typically a state or territory).
-
B.
typeOfMonarchConsort
Indicates the specific kind or category of monarch’s spouse (consort) that an entity is, such as queen consort, prince consort, or empress consort.
-
C.
monarchConsortOf
chosen
Indicates that one person is the spouse of a reigning monarch, holding the role of consort to that monarch.
-
D.
monarchConsortInDynasty
Indicates that a person served as the consort (spouse) of a reigning monarch within a specified dynasty.
-
E.
motherIsConsortOf
Indicates that the subject’s mother is the consort (spouse or official partner) of the specified person.
- F. None of above.
Provenance (3 batches)
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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:41 a.m.