Triple
T29154721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniProtKB/TrEMBL |
E739005
|
entity |
| Predicate | usesEvidenceCodes |
P3168
|
FINISHED |
| Object | Inferred from homology |
—
|
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: Inferred from homology | Statement: [UniProtKB/TrEMBL, usesEvidenceCodes, Inferred from homology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEvidenceCodes Context triple: [UniProtKB/TrEMBL, usesEvidenceCodes, Inferred from homology]
-
A.
usedEvidenceType
chosen
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
B.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
evidenceCited
Indicates that one entity is used as supporting evidence or citation for the claims or content of another entity.
-
D.
hasEvidenceItem
Indicates that there exists a specific piece of evidence supporting, illustrating, or justifying the associated entity or claim.
-
E.
hasNoEvidenceOf
Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:44 a.m.