Triple
T36186113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azam Jah |
E1046848
|
entity |
| Predicate | succeededByInFamilyLine |
P27930
|
FINISHED |
| Object | Mukarram Jah |
—
|
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: Mukarram Jah | Statement: [Azam Jah, succeededByInFamilyLine, Mukarram Jah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByInFamilyLine Context triple: [Azam Jah, succeededByInFamilyLine, Mukarram Jah]
-
A.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
-
B.
resultedInSuccessionFrom
Indicates that one entity’s outcome or event directly caused or led to the succession or replacement of another entity.
-
C.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
-
D.
successorInLineage
chosen
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
E.
successorStateFoundedByFamily
Indicates that the successor state was established or founded by the same family (or a specific family) associated with the original state.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 3, 2026, 4:08 p.m.