Triple
T2107992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaumarchaeota |
E42438
|
entity |
| Predicate | oxidizes |
P7195
|
FINISHED |
| Object | ammonia (NH3) |
—
|
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: ammonia (NH3) | Statement: [Thaumarchaeota, oxidizes, ammonia (NH3)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oxidizes Context triple: [Thaumarchaeota, oxidizes, ammonia (NH3)]
-
A.
oxidizer
chosen
Indicates a relationship where one entity acts as an oxidizing agent that accepts electrons from, or promotes the oxidation of, another entity in a chemical process.
-
B.
oxidationStates
Indicates the specific oxidation numbers assigned to an element or atom within a chemical species, reflecting its electron loss or gain state in that context.
-
C.
odor
Indicates that one entity emits, possesses, or is characterized by a particular smell detectable by another entity.
-
D.
reduces
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
E.
modulates
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae03f308190841f5a419bb821f6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.