Triple
T13959301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta variant |
E335749
|
entity |
| Predicate | firstDetectedDate |
P79627
|
FINISHED |
| Object | October 2020 |
—
|
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: October 2020 | Statement: [Delta variant, firstDetectedDate, October 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDetectedDate Context triple: [Delta variant, firstDetectedDate, October 2020]
-
A.
firstDetectedOn
chosen
Indicates the date or time when something was initially observed, discovered, or recorded for the first time.
-
B.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
C.
firstCrashDate
Indicates the date on which the first crash or failure event occurred for the entity in question.
-
D.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
E.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7b2f908190aa32f22298964746 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.