Triple
T28334778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulaiman Khan Karrani |
E717637
|
entity |
| Predicate | consolidatedPowerOf |
P77053
|
FINISHED |
| Object | Karrani dynasty |
—
|
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: Karrani dynasty | Statement: [Sulaiman Khan Karrani, consolidatedPowerOf, Karrani dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidatedPowerOf Context triple: [Sulaiman Khan Karrani, consolidatedPowerOf, Karrani dynasty]
-
A.
securedPowerBy
Indicates that one entity has obtained or guaranteed power, authority, or control through the involvement, support, or actions of another entity.
-
B.
consolidatedBy
chosen
Indicates that one entity has been merged, unified, or combined into a more cohesive whole by another entity.
-
C.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
D.
consolidatedUnder
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
-
E.
coTrusteePower
Indicates that one trustee holds powers or authority that are shared with one or more co-trustees in administering a trust.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bd3f9288190ad68a1b7e7b0a76d |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:35 a.m.