Triple
T8813450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhizobium |
E209718
|
entity |
| Predicate | carriesGenesFor |
P76194
|
FINISHED |
| Object | nodulation (nod genes) |
—
|
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: nodulation (nod genes) | Statement: [Rhizobium, carriesGenesFor, nodulation (nod genes)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriesGenesFor Context triple: [Rhizobium, carriesGenesFor, nodulation (nod genes)]
-
A.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
B.
isCarrierOf
chosen
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
-
C.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
D.
alsoCarries
Indicates that an entity, in addition to other items or responsibilities it has, carries another specified item or load as well.
-
E.
hasGeneticEvidence
Indicates that there is genetic data or analysis supporting the existence, validity, or nature of the specified relationship or association between entities.
- 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.