Triple
T14993301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HUMINT |
E373890
|
entity |
| Predicate | canBeVulnerableTo |
P583
|
FINISHED |
| Object | deception |
—
|
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: deception | Statement: [HUMINT, canBeVulnerableTo, deception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeVulnerableTo Context triple: [HUMINT, canBeVulnerableTo, deception]
-
A.
susceptibleTo
chosen
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
B.
associatedWithVulnerability
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
C.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
D.
canBeEntangledIn
Indicates that one entity is capable of becoming physically or conceptually caught, intertwined, or ensnared within another entity or situation.
-
E.
isThreatenedCategory
Indicates that an entity belongs to a category facing risk of harm, decline, or extinction.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded716ebb481908224d2d4f7561b03 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.