Triple
T14427079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pPCP1 |
E357723
|
entity |
| Predicate | hasGene |
P114245
|
FINISHED |
| Object | pla |
—
|
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: pla | Statement: [pPCP1, hasGene, pla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGene Context triple: [pPCP1, hasGene, pla]
-
A.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
B.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
-
C.
hasGeneticMechanism
Indicates that one entity possesses or involves a specific genetic process or mechanism responsible for a trait, function, or effect in another entity.
-
D.
hasGeneticEvidence
Indicates that there is genetic data or analysis supporting the existence, validity, or nature of the specified relationship or association between entities.
-
E.
hasGeneticAffiliation
Indicates that one entity is genetically related or affiliated with another, such as sharing ancestry, lineage, or genetic characteristics.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.