Triple
T27526351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saba Ali Khan |
E694848
|
entity |
| Predicate | paternalFamilyTitle |
P20415
|
FINISHED |
| Object | Nawab of Pataudi |
E1780236
|
NE 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: Nawab of Pataudi | Statement: [Saba Ali Khan, paternalFamilyTitle, Nawab of Pataudi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalFamilyTitle Context triple: [Saba Ali Khan, paternalFamilyTitle, Nawab of Pataudi]
-
A.
paternalTitleFamily
Indicates a familial relationship where one entity holds a paternal title (such as father, grandfather, or paternal ancestor) in relation to another within a family structure.
-
B.
paternalTitleInherited
Indicates that an individual has received a title or rank through inheritance from their father.
-
C.
fatherTitle
chosen
Indicates the formal title or designation held by a person's father.
-
D.
paternalTitleConnection
Indicates a relationship where one entity holds a paternal (father-related) title in connection to another entity.
-
E.
fatherTitleAtBirth
Indicates the formal title or honorific held by a person's father at the time of that person's birth.
- F. None of above.
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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f305ce48190ae2a08d4ad2ba05e |
completed | May 2, 2026, 5:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a13032c81e88190a3f5d689bd1b9bff |
completed | May 24, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:24 p.m.