Triple
T23399758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JC virus |
E559470
|
entity |
| Predicate | reactivationOutcome |
P152112
|
FINISHED |
| Object | viremia |
—
|
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: viremia | Statement: [JC virus, reactivationOutcome, viremia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactivationOutcome Context triple: [JC virus, reactivationOutcome, viremia]
-
A.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
-
B.
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.
-
C.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
D.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
-
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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dedfcc8190ab93cec3c3d15c53 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:37 p.m.