Triple
T26870382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PARNAS party |
E676594
|
entity |
| Predicate | stanceOnSecurityServices |
P89137
|
FINISHED |
| Object | limiting powers of security agencies |
—
|
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: limiting powers of security agencies | Statement: [PARNAS party, stanceOnSecurityServices, limiting powers of security agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnSecurityServices Context triple: [PARNAS party, stanceOnSecurityServices, limiting powers of security agencies]
-
A.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
B.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
-
C.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
D.
positionOnSecurity
chosen
Indicates the stance, opinion, or policy an entity holds regarding security-related issues or measures.
-
E.
securityReason
Indicates that something occurs, is restricted, or is justified due to concerns about safety, protection, or maintaining security.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:32 a.m.