Triple
T30922407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Khanum |
E787762
|
entity |
| Predicate | monarchConsortInDynasty |
P174421
|
FINISHED |
| Object | Safavid dynasty |
—
|
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: Safavid dynasty | Statement: [Anna Khanum, monarchConsortInDynasty, Safavid dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchConsortInDynasty Context triple: [Anna Khanum, monarchConsortInDynasty, Safavid dynasty]
-
A.
monarchConsortOf
Indicates that one person is the spouse of a reigning monarch, holding the role of consort to that monarch.
-
B.
monarchOfConsort
Indicates that one entity is the consort (spouse) of the reigning monarch of another entity (typically a state or territory).
-
C.
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.
-
D.
monarchInFamily
Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
-
E.
monarchFather
Indicates that one entity is the male parent (father) of another entity in a monarchical or royal lineage.
- F. None of above. chosen
Provenance (4 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: April 29, 2026, 8:51 p.m.