Triple
T26987917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walkers |
E679782
|
entity |
| Predicate | infectionEffect |
P73777
|
FINISHED |
| Object | Death followed by reanimation |
—
|
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: Death followed by reanimation | Statement: [Walkers, infectionEffect, Death followed by reanimation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infectionEffect Context triple: [Walkers, infectionEffect, Death followed by reanimation]
-
A.
infectionType
Indicates the specific category or nature of an infection associated with an entity or event.
-
B.
infectionPhase
Indicates the specific stage or period within the course of an infection that an entity is currently experiencing.
-
C.
infectionResult
chosen
Indicates that one entity causes or leads to a particular outcome, condition, or state as a result of an infection affecting another entity.
-
D.
toxinEffect
Indicates the harmful impact or physiological response caused by a toxin on a target entity.
-
E.
infectsTissue
Indicates that one entity (typically a pathogen or agent) invades and establishes itself within the tissue of another entity.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6215b9bc881909614a84c9f0dc499 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:50 a.m.