Triple
T5384558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Protective Service of Russia |
E113170
|
entity |
| Predicate | securityClearanceRequired |
P36363
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Federal Protective Service of Russia, securityClearanceRequired, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityClearanceRequired Context triple: [Federal Protective Service of Russia, securityClearanceRequired, high]
-
A.
hasClearance
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
-
B.
clearanceRequired
chosen
Indicates that a specific level of authorization or security clearance is needed before the related action can be performed or access can be granted.
-
C.
hasClearanceBelow
Indicates that one entity’s clearance level is lower than another entity’s clearance level.
-
D.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
-
E.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86f39edc81908e53973cef1bc0f3 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.