Triple
T29797484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza officinalis |
E756592
|
entity |
| Predicate | hasPloidyLevel |
P14755
|
FINISHED |
| Object | tetraploid |
—
|
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: tetraploid | Statement: [Oryza officinalis, hasPloidyLevel, tetraploid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPloidyLevel Context triple: [Oryza officinalis, hasPloidyLevel, tetraploid]
-
A.
ploidyOfSporophyte
chosen
Indicates the number of chromosome sets (ploidy level) present in the sporophyte stage of an organism’s life cycle.
-
B.
hasBalancerChromosomes
Indicates that an organism or genetic sample possesses balancer chromosomes used to maintain specific genetic configurations or prevent recombination.
-
C.
ploidyOfGametophyte
Indicates the number of chromosome sets present in the gametophyte stage of an organism’s life cycle.
-
D.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
E.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
- 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_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 5:16 p.m.