Triple
T8813428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhizobium |
E209718
|
entity |
| Predicate | inducesFormationOf |
P21716
|
FINISHED |
| Object | root nodules |
—
|
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: root nodules | Statement: [Rhizobium, inducesFormationOf, root nodules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inducesFormationOf Context triple: [Rhizobium, inducesFormationOf, root nodules]
-
A.
influencedFormationOf
chosen
Indicates that one entity played a significant role in shaping, initiating, or contributing to the development or establishment of another entity.
-
B.
sporeFormation
Indicates the process by which an organism produces and releases spores as a means of reproduction, survival, or dispersal.
-
C.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
D.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
E.
associatedFormation
Indicates that one entity is linked or connected to a particular formation, such as a geological, structural, or organizational configuration.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff02e9c819080a8e45ba9ca044e |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.