Triple
T29154712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniProtKB/TrEMBL |
E739005
|
entity |
| Predicate | awaitsCurationStatus |
P13062
|
FINISHED |
| Object | expert curation |
—
|
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: expert curation | Statement: [UniProtKB/TrEMBL, awaitsCurationStatus, expert curation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awaitsCurationStatus Context triple: [UniProtKB/TrEMBL, awaitsCurationStatus, expert curation]
-
A.
curationStatus
Indicates the current stage or condition of an item within a curation or review workflow (e.g., pending, approved, rejected, or in progress).
-
B.
submissionStatus
Indicates the current state or phase of a submitted item within a review or processing workflow.
-
C.
collectingStatus
Indicates the current state or phase of an ongoing collection process or activity.
-
D.
seeksStatusAs
chosen
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
E.
isCurated
Indicates that an entity has been deliberately selected, organized, or managed according to specific criteria or standards.
- 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_69f662a87a6c8190b623bacb42af0097 |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:44 a.m.