Triple
T7944514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SolarWinds |
E184465
|
entity |
| Predicate | customersAffectedByIncident |
P56117
|
FINISHED |
| Object | multiple U.S. government 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: multiple U.S. government agencies | Statement: [SolarWinds, customersAffectedByIncident, multiple U.S. government agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customersAffectedByIncident Context triple: [SolarWinds, customersAffectedByIncident, multiple U.S. government agencies]
-
A.
estimatedAffectedPeople
Indicates the estimated number of people expected to be impacted by a particular event, condition, or action.
-
B.
affectedPeople
chosen
Indicates the people who are impacted or influenced by a particular event, action, or condition.
-
C.
affectedCompany
Indicates that a company is impacted or influenced by a particular event, action, or entity.
-
D.
affectedProvision
Indicates that a particular legal provision is impacted, modified, or influenced by another action, decision, or provision.
-
E.
summitAffected
Indicates that a summit, meeting, or high-level event has been influenced, impacted, or altered by a specified factor or circumstance.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0e84448190a7e8e0749776a592 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.