Triple
T37290787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirs of Hunza |
E925659
|
entity |
| Predicate | lastRulingMir |
P48946
|
FINISHED |
| Object | Mir Muhammad Jamal 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: Mir Muhammad Jamal Khan | Statement: [Mirs of Hunza, lastRulingMir, Mir Muhammad Jamal Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastRulingMir Context triple: [Mirs of Hunza, lastRulingMir, Mir Muhammad Jamal Khan]
-
A.
finalRuler
chosen
Indicates that an entity is the last or ultimate ruler of another entity, with no subsequent rulers following.
-
B.
hasRulingIn
Indicates that an authority or decision-making body has issued a formal ruling or judgment within a specified case, context, or jurisdiction.
-
C.
lastHeir
Indicates that one entity is the final remaining heir in a line of succession to another entity’s estate, title, or inheritance.
-
D.
laterRulingClan
Indicates that one clan came to rule or hold power after another clan in a temporal succession.
-
E.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.