Triple
T8674914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarsanism |
E205889
|
entity |
| Predicate | syncreticallyIncorporates |
P19097
|
FINISHED |
| Object | Islamic elements |
—
|
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: Islamic elements | Statement: [Yarsanism, syncreticallyIncorporates, Islamic elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: syncreticallyIncorporates Context triple: [Yarsanism, syncreticallyIncorporates, Islamic elements]
-
A.
laterSyncretizedWith
Indicates that one element was subsequently merged or conflated with another into a single, combined form or identity.
-
B.
religiousSyncretism
chosen
Indicates a blending or merging of elements from different religious traditions into a combined or hybrid belief or practice.
-
C.
egyptianSyncretism
Indicates a relationship where distinct Egyptian deities, cults, or religious concepts are merged or identified with one another (or with foreign counterparts) into a unified or composite form.
-
D.
synonym
Indicates that two terms have the same or nearly the same meaning in a given context.
-
E.
heteronym
Indicates that two or more words share the same spelling but differ in pronunciation and meaning.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.