Triple
T26960257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shefa-'Amr |
E679020
|
entity |
| Predicate | isMultiReligious |
P161377
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shefa-'Amr, isMultiReligious, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultiReligious Context triple: [Shefa-'Amr, isMultiReligious, true]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
ethnicReligionMix
Indicates a relationship where a group or context involves a combined or overlapping presence of specific ethnic identities and religious affiliations.
-
C.
hasPrimaryReligionComplex
Indicates that an entity is primarily associated with, practices, or is characterized by a particular religion or religious complex.
-
D.
hasSecondaryReligion
Indicates that an entity practices, adheres to, or is associated with a secondary religion in addition to its primary religion.
-
E.
isNonReligious
Indicates that an entity does not adhere to, practice, or identify with any religion or religious belief system.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620eb9cd08190a46e909f8496c1da |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:30 a.m.