Triple
T7405286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senhadja de Srair language |
E170853
|
entity |
| Predicate | spokenByReligion |
P76582
|
FINISHED |
| Object | predominantly Muslim speakers |
—
|
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: predominantly Muslim speakers | Statement: [Senhadja de Srair language, spokenByReligion, predominantly Muslim speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenByReligion Context triple: [Senhadja de Srair language, spokenByReligion, predominantly Muslim speakers]
-
A.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
B.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
C.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
D.
religiousGroupMentioned
Indicates that a religious group is referenced or mentioned in the given context or statement.
-
E.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f271f1d481909a46d50b13b51a62 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.