Triple
T29456512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD32 |
E747115
|
entity |
| Predicate | hasIsoform |
P170165
|
FINISHED |
| Object | activating FcγRIIA |
—
|
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: activating FcγRIIA | Statement: [CD32, hasIsoform, activating FcγRIIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIsoform Context triple: [CD32, hasIsoform, activating FcγRIIA]
-
A.
isoformNumber
Indicates the specific variant index or identifier assigned to one isoform among multiple alternative forms of the same gene or protein.
-
B.
alternativeSplicingFeature
Indicates that a genomic region or element participates in an alternative splicing event, distinguishing it as a feature involved in generating splice variants.
-
C.
minorIsoform
Indicates that one biological isoform is a less prevalent or secondary variant relative to another isoform.
-
D.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
E.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 28, 2026, 3:46 p.m.