Triple
T22483140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taysir |
E555814
|
entity |
| Predicate | commonInReligionContext |
P9028
|
FINISHED |
| Object | Islamic cultures |
—
|
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 cultures | Statement: [Taysir, commonInReligionContext, Islamic cultures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInReligionContext Context triple: [Taysir, commonInReligionContext, Islamic cultures]
-
A.
typicalReligionContext
Indicates the usual or most common religious setting, tradition, or affiliation associated with an entity or situation.
-
B.
religionCommon
Indicates that the related entities share the same religion or religious affiliation.
-
C.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
-
D.
associatedReligionOrBelief
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
-
E.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3b03d881909e286a124c1a2b1c |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.