Triple
T1552983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSB |
E33134
|
entity |
| Predicate | securitySector |
P3815
|
FINISHED |
| Object | intelligence |
—
|
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: intelligence | Statement: [FSB, securitySector, intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securitySector Context triple: [FSB, securitySector, intelligence]
-
A.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
B.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
-
C.
securityAspect
chosen
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
D.
sectorProtected
Indicates that a particular sector or area is safeguarded from harm, access, or exploitation by some form of protection or regulation.
-
E.
securityAgency
Indicates that one entity functions as a security agency responsible for protection, surveillance, or enforcement activities in relation to another 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.