Triple
T28818164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteobacteria |
E727687
|
entity |
| Predicate | includesNitrogenFixingBacteria |
P199502
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Proteobacteria, includesNitrogenFixingBacteria, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNitrogenFixingBacteria Context triple: [Proteobacteria, includesNitrogenFixingBacteria, yes]
-
A.
typeOfNitrogenFixation
Indicates the specific kind or method of nitrogen fixation associated with an entity (e.g., biological, industrial, or environmental process).
-
B.
includesNitrifyingBacteria
Indicates that the subject contains or incorporates nitrifying bacteria as part of its composition or system.
-
C.
estimatedShareOfHumanNitrogenFixation
Indicates the proportion of total human-driven nitrogen fixation that is attributed to a given entity or process.
-
D.
isActinorhizalPlant
Indicates that a plant forms a symbiotic, nitrogen-fixing association with actinorhizal (Frankia) bacteria in its roots.
-
E.
fixesNitrogen
Indicates that the subject converts atmospheric nitrogen into biologically usable forms through nitrogen fixation.
- F. None of above. chosen
Provenance (4 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
| PDg | Predicate description generation | batch_69ff3fb151008190bf8a90f9f1c5f0c8 |
completed | May 9, 2026, 2:07 p.m. |
Created at: April 28, 2026, 6:33 a.m.