Triple
T2042656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuristani people |
E44778
|
entity |
| Predicate | conversionToIslam |
P28896
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Nuristani people, conversionToIslam, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToIslam Context triple: [Nuristani people, conversionToIslam, late 19th century]
-
A.
convertedToIslamWith
Indicates that one entity adopted Islam through the influence, guidance, or involvement of another entity.
-
B.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
C.
religiousConversionPeriod
chosen
Indicates the time span during which an entity undergoes or is involved in a process of religious conversion.
-
D.
reconvertedToMosqueBy
Indicates that a building or site, previously used for another purpose, was changed back into a mosque by a specific agent or authority.
-
E.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abbc2c3f6c8190aff07097b2654e52 |
completed | March 7, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69abb7aa00d4819086d347d9a08f81a0 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.