Triple
T17092941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | influenza virus neuraminidase |
E414768
|
entity |
| Predicate | hasActiveSiteResidue |
P125865
|
FINISHED |
| Object | tyrosine 406 (in N2 numbering) |
—
|
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: tyrosine 406 (in N2 numbering) | Statement: [influenza virus neuraminidase, hasActiveSiteResidue, tyrosine 406 (in N2 numbering)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActiveSiteResidue Context triple: [influenza virus neuraminidase, hasActiveSiteResidue, tyrosine 406 (in N2 numbering)]
-
A.
hasActiveMetabolite
Indicates that a substance produces one or more metabolites that remain pharmacologically active in the body.
-
B.
hasNeighboringSite
Indicates that one site is located adjacent to or directly next to another site.
-
C.
hasSiteStatus
Indicates the current operational or condition status assigned to a particular site.
-
D.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
E.
hasActiveNucleus
Indicates that the referenced entity possesses a nucleus that is currently functioning or exhibiting biological activity.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfabf548190a0d37bab3d4ef2fa |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.