Triple
T23399776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JC virus |
E559470
|
entity |
| Predicate | cellEntryReceptor |
P92932
|
FINISHED |
| Object | serotonin receptor 5-HT2A |
—
|
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: serotonin receptor 5-HT2A | Statement: [JC virus, cellEntryReceptor, serotonin receptor 5-HT2A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellEntryReceptor Context triple: [JC virus, cellEntryReceptor, serotonin receptor 5-HT2A]
-
A.
targetCellEntryReceptor
chosen
Indicates that a receptor mediates or enables the entry of a target cell (or agent) into another cell.
-
B.
receptor
Indicates that one entity functions as a receptor for another, typically binding or receiving a signal, substance, or stimulus from it.
-
C.
targetsReceptor
Indicates that one entity is directed toward, binds to, or is designed to act upon a specific receptor.
-
D.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
-
E.
cellInteractionType
Indicates the specific kind of interaction or relationship occurring between cells, such as communication, adhesion, or signaling.
- 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_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. |
Created at: April 17, 2026, 5:37 p.m.