Triple
T9461523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | نورستانیان |
E228156
|
entity |
| Predicate | دین تاریخی |
P28785
|
FINISHED |
| Object | ادیان بومی چندخدایی پیشااسلامی |
—
|
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: ادیان بومی چندخدایی پیشااسلامی | Statement: [نورستانیان, دین تاریخی, ادیان بومی چندخدایی پیشااسلامی]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: دین تاریخی Context triple: [نورستانیان, دین تاریخی, ادیان بومی چندخدایی پیشااسلامی]
-
A.
historicalDoctrine
chosen
Indicates that one entity embodies, represents, or is associated with a doctrine, teaching, or set of principles originating from a past historical context.
-
B.
dynasticReligion
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
-
C.
الديانة
Indicates the religious affiliation or faith tradition that an entity follows or is associated with.
-
D.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
E.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcc8b1881908aa6ee13ab195330 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.