Triple
T29797513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza officinalis |
E756592
|
entity |
| Predicate | isGeneSourceFor |
P114245
|
FINISHED |
| Object | disease resistance genes in 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: disease resistance genes in cultivated rice | Statement: [Oryza officinalis, isGeneSourceFor, disease resistance genes in cultivated rice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeneSourceFor Context triple: [Oryza officinalis, isGeneSourceFor, disease resistance genes in cultivated rice]
-
A.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
B.
hasGene
chosen
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
C.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
D.
isEndogenousTo
Indicates that something originates from, is produced within, or is internally determined by the system, organism, or context it is associated with.
-
E.
isExtendedSource
Indicates that the source is spatially extended rather than point-like in the observed data or image.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e7548c81909acffee32ca126f9 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:16 p.m.