Triple
T31535669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aromatic L-amino acid decarboxylase |
E804593
|
entity |
| Predicate | hasEnzymeCommissionClass |
P31231
|
FINISHED |
| Object | carboxy-lyases |
—
|
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: carboxy-lyases | Statement: [aromatic L-amino acid decarboxylase, hasEnzymeCommissionClass, carboxy-lyases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnzymeCommissionClass Context triple: [aromatic L-amino acid decarboxylase, hasEnzymeCommissionClass, carboxy-lyases]
-
A.
hasEnzymeCommissionNumber
Indicates that an entity is associated with a specific Enzyme Commission (EC) number that classifies its enzymatic activity.
-
B.
hasEnzymeActivity
Indicates that an entity performs or exhibits a specific enzyme-catalyzed biochemical activity.
-
C.
enzymeType
chosen
Indicates the specific class or category of enzyme associated with an entity or reaction.
-
D.
actsOnEnzyme
Indicates that one entity performs an action that affects the activity, function, or state of an enzyme.
-
E.
isSynthesizedByEnzyme
Indicates that a substance or molecule is produced or formed through the catalytic action of a specific enzyme.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 30, 2026, 10:03 p.m.