Triple
T3297152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hausa people |
E69242
|
entity |
| Predicate | majorReligionIntroduced |
P18407
|
FINISHED |
| Object | Islam in the 11th 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: Islam in the 11th century | Statement: [Hausa people, majorReligionIntroduced, Islam in the 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorReligionIntroduced Context triple: [Hausa people, majorReligionIntroduced, Islam in the 11th century]
-
A.
religionIntroduced
chosen
Indicates that one entity brought or established a particular religion or religious tradition to another entity, place, or group for the first time.
-
B.
promotedReligion
Indicates that an entity actively supported, advocated for, or worked to spread a particular religion.
-
C.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
-
D.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
E.
containsMajorReligionOrigin
Indicates that a location is the place where a major religion first originated or was founded.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb078f3dc8190afb624f62894e48f |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.