Triple
T37043108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shahiya dynasty |
E916833
|
entity |
| Predicate | lastMajorHinduPowerInRegion |
P186936
|
FINISHED |
| Object | eastern Afghanistan |
—
|
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: eastern Afghanistan | Statement: [Shahiya dynasty, lastMajorHinduPowerInRegion, eastern Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMajorHinduPowerInRegion Context triple: [Shahiya dynasty, lastMajorHinduPowerInRegion, eastern Afghanistan]
-
A.
governedIndiaUntil
Indicates that a subject held governing authority over India up to a specified end time or date.
-
B.
countryDuringMughalEra
Indicates that a modern or historical country existed within, or is being considered in the context of, the Mughal Empire’s period of rule.
-
C.
lastSuzerainPower
Indicates that one entity is the most recent or final suzerain (overlord power) exercising dominant authority over another entity.
-
D.
lastReigningMonarchAccessionToIndiaYear
Indicates the year in which the last reigning monarch formally acceded to India.
-
E.
lastRulingKingdom
Indicates that one entity is the final or most recent kingdom to have ruled over the other entity.
- F. None of above. chosen
Provenance (4 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.