Triple

T27756099
Position Surface form Disambiguated ID Type / Status
Subject Love Letter worm E701335 entity
Predicate damageEstimateUSD P25888 FINISHED
Object 5000000000 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: 5000000000 | Statement: [Love Letter worm, damageEstimateUSD, 5000000000]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: damageEstimateUSD
Context triple: [Love Letter worm, damageEstimateUSD, 5000000000]
  • A. economicDamageApprox chosen
    Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
  • B. economicDamage
    Indicates that one entity causes or experiences financial loss, harm, or negative economic impact as a result of another entity or event.
  • C. economicDamageRank
    Indicates the relative severity or position of an entity in terms of the economic damage it causes or experiences compared to others.
  • D. estimatedCost
    Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
  • E. damageCostNote
    Indicates a descriptive note or explanation associated with the cost of damage, providing contextual or clarifying information about that damage-related expense.
  • 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_69ef6a5193808190816eb7d0020b2d87 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63760b350819088f0eca0257ca125 completed May 2, 2026, 5:41 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
Created at: April 27, 2026, 4:23 p.m.