Triple
T25822402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severe Threat Level |
E650436
|
entity |
| Predicate | communicationMediums |
P2798
|
FINISHED |
| Object | government websites |
—
|
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: government websites | Statement: [Severe Threat Level, communicationMediums, government websites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationMediums Context triple: [Severe Threat Level, communicationMediums, government websites]
-
A.
mediumOfCommunicationFor
Indicates that one entity serves as the medium or channel through which another entity communicates or conveys information.
-
B.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
C.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
D.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
E.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 7:30 a.m.