Triple

T29154714
Position Surface form Disambiguated ID Type / Status
Subject UniProtKB/TrEMBL E739005 entity
Predicate hasCurationLevel P107343 FINISHED
Object unreviewed entries 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: unreviewed entries | Statement: [UniProtKB/TrEMBL, hasCurationLevel, unreviewed entries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCurationLevel
Context triple: [UniProtKB/TrEMBL, hasCurationLevel, unreviewed entries]
  • A. curationLevel chosen
    Indicates the degree or extent to which something has been deliberately selected, organized, or refined by a curator or curatorial process.
  • B. isCurated
    Indicates that an entity has been deliberately selected, organized, or managed according to specific criteria or standards.
  • C. curationStatus
    Indicates the current stage or condition of an item within a curation or review workflow (e.g., pending, approved, rejected, or in progress).
  • D. hasCuratorialScope
    Indicates the specific thematic, temporal, geographic, or collection focus that defines the boundaries of an entity’s curatorial responsibility or activity.
  • E. hasCuratorialModel
    Indicates that one entity employs, follows, or is governed by a particular curatorial model defined by 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_69f07cb46f148190874eb8576a447567 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69fb563aec448190875410fb1a3ed624 completed May 6, 2026, 2:54 p.m.
PD Predicate disambiguation batch_69fb35b9ede881908aaae93a215525df completed May 6, 2026, 12:36 p.m.
Created at: April 28, 2026, 11:44 a.m.