Triple
T17093359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesicular stomatitis virus |
E414778
|
entity |
| Predicate | notableProtein |
P112356
|
FINISHED |
| Object | glycoprotein G |
—
|
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: glycoprotein G | Statement: [Vesicular stomatitis virus, notableProtein, glycoprotein G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProtein Context triple: [Vesicular stomatitis virus, notableProtein, glycoprotein G]
-
A.
proteinContent
Indicates the amount or proportion of protein present in a given entity or substance.
-
B.
hasProtein
chosen
Indicates that one entity contains, includes, or is associated with a specific protein.
-
C.
nutritionComponent
Indicates that one entity is a nutritional constituent, ingredient, or component of another (typically a food, diet, or nutritional product).
-
D.
mainProtein
Indicates that one protein is the primary or central protein in relation to another entity, such as a complex, pathway, or interaction context.
-
E.
nutritionalRequirement
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfb89348190942984037bd3bd2e |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.