Triple
T27756136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Bug |
E701336
|
entity |
| Predicate | causedDamageType |
P22116
|
FINISHED |
| Object | data loss |
—
|
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: data loss | Statement: [Love Bug, causedDamageType, data loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causedDamageType Context triple: [Love Bug, causedDamageType, data loss]
-
A.
hasTypeOfDamage
Indicates that an entity experiences or exhibits a specific kind or category of damage.
-
B.
primaryDamageType
chosen
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
C.
damageClass
Indicates the type or category of damage associated with an action, event, or interaction between entities.
-
D.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
E.
coversDamageType
Indicates that one entity provides protection, compensation, or applicability for a specified type of damage.
- 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_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 4:23 p.m.