Triple
T26960222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Sindh Frontier |
E679019
|
entity |
| Predicate | preColonialRulers |
P8531
|
FINISHED |
| Object | Talpur 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: Talpur dynasty | Statement: [Upper Sindh Frontier, preColonialRulers, Talpur dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preColonialRulers Context triple: [Upper Sindh Frontier, preColonialRulers, Talpur dynasty]
-
A.
historicalRulers
chosen
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
B.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
C.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
D.
ethnicGroupOfRulers
Indicates the ethnic group to which the rulers of a given political or territorial entity belong or belonged.
-
E.
colonialPowerBefore
Indicates that one entity served as the colonial ruling power over another entity during an earlier, preceding time period.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620eb9cd08190a46e909f8496c1da |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:30 a.m.