Triple
T29529343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarsani faith |
E749154
|
entity |
| Predicate | relationshipToIslam |
P41928
|
FINISHED |
| Object | distinct from mainstream Islam |
—
|
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: distinct from mainstream Islam | Statement: [Yarsani faith, relationshipToIslam, distinct from mainstream Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToIslam Context triple: [Yarsani faith, relationshipToIslam, distinct from mainstream Islam]
-
A.
relationToIslam
chosen
Indicates how an entity is connected or related to Islam, such as through belief, practice, affiliation, or influence.
-
B.
relationshipToReligion
Indicates the nature or type of connection an entity has to a religion, such as affiliation, stance, or involvement.
-
C.
positionOnIslam
Indicates the stance, viewpoint, or attitude that an entity holds toward Islam.
-
D.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
-
E.
familyRelationInIslamicTradition
Indicates a familial relationship as defined within Islamic tradition, including kinship ties, marital bonds, and lineage-based connections governed by Islamic law and customs.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
Created at: April 28, 2026, 4:51 p.m.