Triple
T25094026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalhoro |
E628539
|
entity |
| Predicate | foundingRulerOfDynasty |
P114665
|
FINISHED |
| Object | Mian Yar Muhammad Kalhoro |
E631814
|
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: Mian Yar Muhammad Kalhoro | Statement: [Kalhoro, foundingRulerOfDynasty, Mian Yar Muhammad Kalhoro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingRulerOfDynasty Context triple: [Kalhoro, foundingRulerOfDynasty, Mian Yar Muhammad Kalhoro]
-
A.
founderDynasty
Indicates that an entity is the founding member or originator of a particular dynasty.
-
B.
foundingDynastyOf
Indicates that a particular dynasty is the original founding ruling house or lineage of a specified political entity, state, or realm.
-
C.
governingDynastyAtFoundation
Indicates the ruling dynasty that held power at the time an entity (such as a state, city, or institution) was founded.
-
D.
dynastyFoundedRuledRegion
Indicates that a particular dynasty was established and exercised ruling authority over a specified region.
-
E.
dynastyFoundedByMember
chosen
Indicates that a dynasty was established or initiated by a specific individual who is a member of that dynasty.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1048ea21148190b688671c8d8aff35 |
completed | May 22, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:24 a.m.