Triple
T12253373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bir al-Abd |
E292031
|
entity |
| Predicate | regionalSecurityContext |
P32691
|
FINISHED |
| Object | part of North Sinai security zone |
—
|
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: part of North Sinai security zone | Statement: [Bir al-Abd, regionalSecurityContext, part of North Sinai security zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalSecurityContext Context triple: [Bir al-Abd, regionalSecurityContext, part of North Sinai security zone]
-
A.
securityContext
Indicates the security-related settings or constraints under which an action, process, or interaction is performed.
-
B.
regionContext
chosen
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
C.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
-
D.
securityScope
Indicates the range or extent of protection, permissions, or access control that applies within a given security context.
-
E.
includesRegionalSecurityFramework
Indicates that an entity incorporates or is part of a broader regional security cooperation or defense framework.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.