Triple
T8243706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night Surf |
E192796
|
entity |
| Predicate | hasPandemicCause |
P81116
|
FINISHED |
| Object | mutated influenza-like virus |
—
|
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: mutated influenza-like virus | Statement: [Night Surf, hasPandemicCause, mutated influenza-like virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPandemicCause Context triple: [Night Surf, hasPandemicCause, mutated influenza-like virus]
-
A.
associatedPandemic
Indicates a relationship where something (such as an event, condition, or entity) is linked or connected to a specific pandemic.
-
B.
associatedWithEpidemic
Indicates that something has a connection or relevance to an epidemic, such as being caused by, occurring during, or contributing to that epidemic.
-
C.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
D.
isCarrierOf
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
-
E.
experiencedEpidemic
Indicates that an entity has undergone or been affected by an epidemic event.
- F. None of above. chosen
Provenance (4 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78711f5081909c2f357334491a07 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb447c146081909decf97bbd26c496 |
completed | March 31, 2026, 3:50 a.m. |
Created at: March 30, 2026, 5:47 p.m.