Triple
T25094017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalhoro |
E628539
|
entity |
| Predicate | dynastyProvided |
P157636
|
FINISHED |
| Object | Kalhora dynasty |
E160201
|
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: Kalhora dynasty | Statement: [Kalhoro, dynastyProvided, Kalhora dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyProvided Context triple: [Kalhoro, dynastyProvided, Kalhora dynasty]
-
A.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
B.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
C.
dynastyContext
Indicates the historical or cultural dynasty within which an entity, event, or relationship is situated or contextualized.
-
D.
dynastyInvolved
Indicates that a particular dynasty participates in, is associated with, or plays a role in the referenced event, process, or situation.
-
E.
dynastyConfirmed
Indicates that a particular ruling dynasty has been officially verified or recognized as legitimate in a given context.
- F. None of above. chosen
Provenance (5 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_69f464b77f94819086b73037950546fc |
completed | May 1, 2026, 8:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1048ea21148190b688671c8d8aff35 |
completed | May 22, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:24 a.m.