Triple
T8813425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhizobium |
E209718
|
entity |
| Predicate | usesEnzyme |
P31231
|
FINISHED |
| Object | nitrogenase |
—
|
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: nitrogenase | Statement: [Rhizobium, usesEnzyme, nitrogenase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEnzyme Context triple: [Rhizobium, usesEnzyme, nitrogenase]
-
A.
enzymeType
chosen
Indicates the specific class or category of enzyme associated with an entity or reaction.
-
B.
hasEnzymeCommissionNumber
Indicates that an entity is associated with a specific Enzyme Commission (EC) number that classifies its enzymatic activity.
-
C.
isMetabolizedBy
Indicates that a substance is biochemically broken down or transformed through metabolic processes carried out by a specified organism, cell type, or enzyme system.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff02e9c819080a8e45ba9ca044e |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.