Triple
T22796911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemin3 |
E564272
|
entity |
| Predicate | hasEnzymeClass |
P31231
|
FINISHED |
| Object | helicase |
—
|
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: helicase | Statement: [Gemin3, hasEnzymeClass, helicase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnzymeClass Context triple: [Gemin3, hasEnzymeClass, helicase]
-
A.
enzymeType
chosen
Indicates the specific class or category of enzyme associated with an entity or reaction.
-
B.
hasChemicalClass
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
-
C.
hasEnzymeCommissionNumber
Indicates that an entity is associated with a specific Enzyme Commission (EC) number that classifies its enzymatic activity.
-
D.
hasMolecularFunction
Indicates that an entity (typically a gene product or protein) performs or is associated with a specific molecular-level activity or function.
-
E.
enzymeSystem
Indicates a relationship where an entity functions as, or is part of, a specific enzyme system involved in catalyzing biochemical reactions.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd9b3c0819096050f43a829ec0d |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.