Triple
T27756247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melissa virus |
E701338
|
entity |
| Predicate | legalConsequenceForCreator |
P36372
|
FINISHED |
| Object | arrest of David L. Smith |
—
|
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: arrest of David L. Smith | Statement: [Melissa virus, legalConsequenceForCreator, arrest of David L. Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalConsequenceForCreator Context triple: [Melissa virus, legalConsequenceForCreator, arrest of David L. Smith]
-
A.
violationConsequences
chosen
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
B.
hasNotableContentCreator
Indicates that an entity is associated with a content creator who is recognized as notable or prominent.
-
C.
consequenceOfRestrictions
Indicates the outcomes or effects that arise as a result of certain restrictions being imposed.
-
D.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
-
E.
contentRestriction
Indicates that access to or use of certain content is limited or controlled based on specified rules or conditions.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 4:23 p.m.