Triple
T28818233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epstein–Barr virus infection |
E727688
|
entity |
| Predicate | reactivationPossible |
P166893
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Epstein–Barr virus infection, reactivationPossible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactivationPossible Context triple: [Epstein–Barr virus infection, reactivationPossible, true]
-
A.
reactivationOutcome
Indicates the result or consequence that follows from a reactivation event or process.
-
B.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
C.
reactivatedFrom
Indicates that an entity has been brought back into an active state from a previously inactive, archived, or decommissioned state, often referencing the source state or version it was reactivated from.
-
D.
canReinstate
Indicates that one entity has the authority or ability to restore another entity or state to a previous valid or active condition.
-
E.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 6:33 a.m.