Triple
T9807410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | programmed death-ligand 1 |
E238185
|
entity |
| Predicate | geneOntologyTerm |
P65649
|
FINISHED |
| Object | GO:0031294 |
—
|
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: GO:0031294 | Statement: [programmed death-ligand 1, geneOntologyTerm, GO:0031294]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneOntologyTerm Context triple: [programmed death-ligand 1, geneOntologyTerm, GO:0031294]
-
A.
ontologyId
chosen
Indicates that there is an association between an entity and a specific ontology identifier that formally defines or classifies it within an ontology.
-
B.
geneSymbol
Indicates the standardized short-form symbol assigned to a specific gene.
-
C.
NCBIGeneID
Indicates a relationship that assigns or links an entity to its unique gene identifier as defined in the NCBI Gene database.
-
D.
geneType
Indicates the specific category or classification of a gene based on its functional or structural characteristics.
-
E.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7ddaac8190a5584a5c863fbaa3 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.