Triple
T6482117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Guard (Bahrain) |
E146418
|
entity |
| Predicate | securityPriority |
P71157
|
FINISHED |
| Object | regime security |
—
|
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: regime security | Statement: [Royal Guard (Bahrain), securityPriority, regime security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityPriority Context triple: [Royal Guard (Bahrain), securityPriority, regime security]
-
A.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
B.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
C.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
D.
securityGoal
Indicates that an action, system, or policy is intended to achieve, support, or satisfy a specified security objective or protection target.
-
E.
securityAspect
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
- 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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6b2e9881908b715573e7ba7458 |
completed | March 22, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c06822f73081908e6bb9edecbe77a6 |
completed | March 22, 2026, 10:07 p.m. |
Created at: March 22, 2026, 4:51 p.m.