Triple
T1392789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talpur dynasty |
E30597
|
entity |
| Predicate | rulingPeriodStart |
P1506
|
FINISHED |
| Object | 1783 |
—
|
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: 1783 | Statement: [Talpur dynasty, rulingPeriodStart, 1783]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingPeriodStart Context triple: [Talpur dynasty, rulingPeriodStart, 1783]
-
A.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
B.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
currentMonarchStart
Indicates the date or point in time when the current monarch’s reign began.
-
D.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
-
E.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
- 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.