Triple
T3100070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British embassies |
E64692
|
entity |
| Predicate | internalSecurityProvidedBy |
P8728
|
FINISHED |
| Object | United Kingdom security staff |
—
|
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: United Kingdom security staff | Statement: [British embassies, internalSecurityProvidedBy, United Kingdom security staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalSecurityProvidedBy Context triple: [British embassies, internalSecurityProvidedBy, United Kingdom security staff]
-
A.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
-
B.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
C.
securityArrangementsBy
chosen
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
D.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
-
E.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26b03a081909cf187b9a8f805ce |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.