Triple
T30527262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza ridleyi |
E776884
|
entity |
| Predicate | hasGeneticDiversity |
P35225
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Oryza ridleyi, hasGeneticDiversity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneticDiversity Context triple: [Oryza ridleyi, hasGeneticDiversity, high]
-
A.
geneticDiversity
chosen
Indicates variation in genetic characteristics within or between populations or groups.
-
B.
hasInternalDiversity
Indicates that an entity contains multiple distinct types, elements, or subgroups within itself, rather than being uniform or homogeneous.
-
C.
hadPopulationDiversity
Indicates that an entity possessed a population characterized by a variety of distinct demographic or group attributes (such as ethnicity, culture, or other differentiating factors).
-
D.
hasGeneticMechanism
Indicates that one entity possesses or involves a specific genetic process or mechanism responsible for a trait, function, or effect in another entity.
-
E.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 8:17 p.m.