Triple
T9738236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitrosopumilus |
E236119
|
entity |
| Predicate | nitrogenCycleRole |
P38725
|
FINISHED |
| Object | ammonia oxidation |
—
|
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 oxidation | Statement: [Nitrosopumilus, nitrogenCycleRole, ammonia oxidation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nitrogenCycleRole Context triple: [Nitrosopumilus, nitrogenCycleRole, ammonia oxidation]
-
A.
roleInBiogeochemistry
chosen
Indicates the function or influence an entity has within biogeochemical cycles and processes.
-
B.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
C.
roleInDiseaseCycle
Indicates the specific function or contribution an entity has within the progression, transmission, or maintenance of a disease over time.
-
D.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
-
E.
roleInEcosystem
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef2ba048190811d6f4251fdb270 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.