Triple
T34091654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G protein–coupled receptors |
E874314
|
entity |
| Predicate | signalThrough |
P64492
|
FINISHED |
| Object | Gs proteins |
—
|
NE NERFINISHED |
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: Gs proteins | Statement: [G protein–coupled receptors, signalThrough, Gs proteins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalThrough Context triple: [G protein–coupled receptors, signalThrough, Gs proteins]
-
A.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
-
B.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
C.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
D.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
-
E.
signalPath
chosen
Indicates that there is a route or connection along which a signal can travel from one entity to another.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c16095081908ffa34ea55556a65 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.