Triple
T19773755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | respiratory syncytial virus |
E474952
|
entity |
| Predicate | attachmentMediatedBy |
P58467
|
FINISHED |
| Object | G protein |
—
|
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: G protein | Statement: [respiratory syncytial virus, attachmentMediatedBy, G protein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachmentMediatedBy Context triple: [respiratory syncytial virus, attachmentMediatedBy, G protein]
-
A.
mediatedIn
chosen
Indicates that an entity acted as an intermediary or facilitator in bringing about, enabling, or influencing another entity or event.
-
B.
attachmentMethod
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
C.
mediatedBetween
Indicates that an entity acted as an intermediary or go-between facilitating interaction, communication, or negotiation between two other entities.
-
D.
attachmentType
Indicates the specific kind or category of attachment that relates one entity to another.
-
E.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535e450c8190a2628245ae0d0bd3 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.