Triple
T20589191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khalil Esfandiary-Bakhtiary |
E505867
|
entity |
| Predicate | relationToMohammadRezaShahPahlavi |
P79058
|
FINISHED |
| Object | father-in-law |
—
|
LITERAL FINISHED |
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: father-in-law | Statement: [Khalil Esfandiary-Bakhtiary, relationToMohammadRezaShahPahlavi, father-in-law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToMohammadRezaShahPahlavi Context triple: [Khalil Esfandiary-Bakhtiary, relationToMohammadRezaShahPahlavi, father-in-law]
-
A.
familyRelationToEmperor
chosen
Indicates that one entity is related to an emperor by family ties, specifying a kinship or familial connection between them.
-
B.
familyRelationToHeadOfState
Indicates the type of familial relationship an individual has to the current head of state.
-
C.
lastReigningShahWhoseWifeHeldTitle
Indicates that the subject is the final Shah to have reigned whose wife held a specific formal title.
-
D.
parentOfRoyalDescendants
Indicates being the parent of one or more individuals who are of royal descent.
-
E.
relationToNurJahan
Indicates a relationship or connection that an entity has specifically to Nur Jahan.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a979e4a48190a948165fb0f3b265 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.