Triple
T26309429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عام الحزن |
E661778
|
entity |
| Predicate | يتضمن_حدث |
P58905
|
FINISHED |
| Object | تزايد الحصار الاجتماعي والدعائي ضد الدعوة الإسلامية |
—
|
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: تزايد الحصار الاجتماعي والدعائي ضد الدعوة الإسلامية | Statement: [عام الحزن, يتضمن_حدث, تزايد الحصار الاجتماعي والدعائي ضد الدعوة الإسلامية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يتضمن_حدث Context triple: [عام الحزن, يتضمن_حدث, تزايد الحصار الاجتماعي والدعائي ضد الدعوة الإسلامية]
-
A.
includesEvents
chosen
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
B.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
C.
حدث_في
Indicates that an event or action took place in or occurred at a specific location or time.
-
D.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:21 p.m.