Triple
T18496588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الحركة المصرية من أجل التغيير |
E451962
|
entity |
| Predicate | نطاق_التأثير |
P75457
|
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.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
B.
hasInfluenceScope
chosen
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
C.
areaOfSupport
Indicates the spatial region or domain within which an entity provides support, assistance, or backing to another.
-
D.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
E.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c09a8081909cf0b44df3682bb8 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.