Triple
T10067379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sesbania |
E213134
|
entity |
| Predicate | biologicalNitrogenFixation |
P4281
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sesbania, biologicalNitrogenFixation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biologicalNitrogenFixation Context triple: [Sesbania, biologicalNitrogenFixation, true]
-
A.
nutrientUptake
Indicates the process by which an entity absorbs or takes in nutrients from its surrounding environment.
-
B.
fixesNitrogen
chosen
Indicates that the subject converts atmospheric nitrogen into biologically usable forms through nitrogen fixation.
-
C.
biota
Indicates the presence or composition of living organisms (flora, fauna, or other life forms) associated with a given entity or environment.
-
D.
affectsBiologicalProcess
Indicates a relationship where one entity produces a change or influence on a biological process of another entity or system.
-
E.
carbonFixationPathway
Indicates that one entity is involved in, or associated with, the biochemical pathway by which inorganic carbon (e.g., CO₂) is converted into organic compounds.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff63a4c8190bb08a0428aafa189 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.