Triple
T18496626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | كفاية |
E451963
|
entity |
| Predicate | موقف من الأمن |
P89137
|
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.
positionOnSecurity
chosen
Indicates the stance, opinion, or policy an entity holds regarding security-related issues or measures.
-
B.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
C.
securityArrangements
Indicates the existence, nature, or details of protective measures or safeguards established between or around entities.
-
D.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
E.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
- 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.