Triple
T1392809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talpur dynasty |
E30597
|
entity |
| Predicate | postConquestStatusOfKhairpur |
P17908
|
FINISHED |
| Object | princely state under British suzerainty |
—
|
LITERAL 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: princely state under British suzerainty | Statement: [Talpur dynasty, postConquestStatusOfKhairpur, princely state under British suzerainty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postConquestStatusOfKhairpur Context triple: [Talpur dynasty, postConquestStatusOfKhairpur, princely state under British suzerainty]
-
A.
statusInPakistan
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
-
B.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
C.
governorOfPunjabAtTheTime
Indicates that one entity held the official position of Governor of Punjab during the time period relevant to the other entity or event.
-
D.
statusInAfghanistan
Indicates the condition, role, or legal standing an entity holds within the context of Afghanistan.
-
E.
postConflictStatus
chosen
Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c360a7f08190ab7e903764b06fdf |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.