Triple
T29852048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glycine canescens |
E758090
|
entity |
| Predicate | belongsToGenePoolOf |
P169736
|
FINISHED |
| Object | soybean |
—
|
NE NERFINISHED |
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: soybean | Statement: [Glycine canescens, belongsToGenePoolOf, soybean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToGenePoolOf Context triple: [Glycine canescens, belongsToGenePoolOf, soybean]
-
A.
isGenePoolFor
chosen
Indicates that one entity serves as the collective genetic reservoir or source population from which the other entity’s members or genetic traits are derived.
-
B.
belongsToPopulation
Indicates that an entity is a member or constituent of a specified population or group.
-
C.
isGeneticUnitOf
Indicates that one entity functions as a genetic component, segment, or element that forms part of, or contributes to, the genetic makeup of another entity.
-
D.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
E.
hasGeneticAffiliation
Indicates that one entity is genetically related or affiliated with another, such as sharing ancestry, lineage, or genetic characteristics.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 5:44 p.m.