Triple
T8548692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dee-geo-woo-gen |
E202390
|
entity |
| Predicate | breedingPurpose |
P32409
|
FINISHED |
| Object | development of semi-dwarf high-yielding 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: development of semi-dwarf high-yielding rice | Statement: [Dee-geo-woo-gen, breedingPurpose, development of semi-dwarf high-yielding rice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingPurpose Context triple: [Dee-geo-woo-gen, breedingPurpose, development of semi-dwarf high-yielding rice]
-
A.
breedingUse
Indicates that one entity is used for breeding or reproductive purposes with respect to another entity.
-
B.
breedingGoal
chosen
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
C.
breedingMethod
Indicates the technique or process by which organisms are bred or reproduced.
-
D.
breedingStatus
Indicates the reproductive condition or phase an entity is currently in, such as whether it is capable of, engaged in, or excluded from breeding.
-
E.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe7529b648190b4b1cf1cb8836546 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.