Triple
T31407122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kandahar–Herat Highway |
E801159
|
entity |
| Predicate | securityRisks |
P91654
|
FINISHED |
| Object | insurgent attacks |
—
|
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: insurgent attacks | Statement: [Kandahar–Herat Highway, securityRisks, insurgent attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityRisks Context triple: [Kandahar–Herat Highway, securityRisks, insurgent attacks]
-
A.
securityImplication
chosen
Indicates that one entity has a consequence, effect, or relevance for the safety, protection, or vulnerability status of another entity or system.
-
B.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
-
C.
securityAttention
Indicates that an entity is the focus of monitoring, concern, or scrutiny from a security perspective.
-
D.
securityAdvisory
Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
-
E.
securityVulnerability
Indicates that an entity has a weakness or flaw that could be exploited to compromise its 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 30, 2026, 8:33 p.m.