Triple

T9311971
Position Surface form Disambiguated ID Type / Status
Subject TweetNaCl E224026 entity
Predicate aimsToAvoid P17548 FINISHED
Object misuse-prone low-level crypto primitives 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: misuse-prone low-level crypto primitives | Statement: [TweetNaCl, aimsToAvoid, misuse-prone low-level crypto primitives]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimsToAvoid
Context triple: [TweetNaCl, aimsToAvoid, misuse-prone low-level crypto primitives]
  • A. designedToAvoid chosen
    Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
  • B. avoidsRoute
    Indicates that an entity deliberately does not use or travel along a particular route.
  • C. triedToAvoid
    Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
  • D. avoidanceStrategy
    Indicates a relationship where one entity deliberately takes actions or adopts behaviors to evade, minimize, or escape interaction, contact, or confrontation with another entity or situation.
  • E. aimsToControl
    Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
  • 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_69ca8425f4fc81909c1c586e9a5b7530 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd20ae96e481909a1af9ea1c91f2b2 completed April 1, 2026, 1:42 p.m.
PD Predicate disambiguation batch_69cc7a61e9a4819096eb014f3791ef2e completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:37 p.m.