Triple
T30138376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathan dynasty |
E766060
|
entity |
| Predicate | notableReligionOfRulers |
P55284
|
FINISHED |
| Object | Sunni Islam |
E11619
|
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: Sunni Islam | Statement: [Pathan dynasty, notableReligionOfRulers, Sunni Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableReligionOfRulers Context triple: [Pathan dynasty, notableReligionOfRulers, Sunni Islam]
-
A.
hasPrimaryReligionOfRulers
chosen
Indicates that the specified religion is the main or official faith practiced or endorsed by the rulers of an entity.
-
B.
religiousRoleOfRuler
Indicates that a ruler holds a specific religious office, function, or authority within a religious system or tradition.
-
C.
rulerReligion
Indicates that a ruler adheres to, practices, or is officially associated with a particular religion.
-
D.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
E.
religionOfConquerors
Indicates that the specified religion is practiced or upheld by the conquering group or power in a given context.
- F. None of above.
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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a274ca889288190b5c2980f09e41510 |
completed | June 8, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:17 p.m.