Triple
T30359816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza grandiglumis |
E772247
|
entity |
| Predicate | isGenePoolFor |
P169736
|
FINISHED |
| Object | cultivated rice |
—
|
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: cultivated rice | Statement: [Oryza grandiglumis, isGenePoolFor, cultivated rice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGenePoolFor Context triple: [Oryza grandiglumis, isGenePoolFor, cultivated rice]
-
A.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
B.
isGSE
Indicates that one entity functions as a ground support equipment (GSE) resource used to support, service, or handle another entity, typically in an aerospace or aviation context.
-
C.
isGSE
Indicates that something is a Gene Set Enrichment (GSE) entity or is associated with a gene set enrichment analysis result.
-
D.
hasGenera
Indicates a taxonomic relationship in which a higher-level group (such as a family or subfamily) includes one or more genera as its subordinate members.
-
E.
isSelfPollinating
Indicates that an organism or plant can fertilize itself without requiring pollen from another individual.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682423e748190b20a754a0f1a9114 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 7:57 p.m.