Triple
T10067526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradyrhizobium |
E213137
|
entity |
| Predicate | benefitsHostBy |
P91922
|
FINISHED |
| Object | providing fixed nitrogen |
—
|
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: providing fixed nitrogen | Statement: [Bradyrhizobium, benefitsHostBy, providing fixed nitrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitsHostBy Context triple: [Bradyrhizobium, benefitsHostBy, providing fixed nitrogen]
-
A.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
-
B.
roleOfHost
Indicates that an entity serves as the host in relation to another entity, event, or interaction.
-
C.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
D.
hostedFirst
Indicates that one entity acted as the initial host for another entity, preceding any subsequent hosts.
-
E.
supportsHosting
Indicates that one entity provides the necessary resources or capabilities for another entity to host or run something (such as an application, service, or content).
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff798bc8190a84af7bedea66f0a |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:58 p.m.