Triple
T11977451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triticum aestivum |
E285072
|
entity |
| Predicate | isBreedingTargetFor |
P32409
|
FINISHED |
| Object | disease resistance |
—
|
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 | Statement: [Triticum aestivum, isBreedingTargetFor, disease resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBreedingTargetFor Context triple: [Triticum aestivum, isBreedingTargetFor, disease resistance]
-
A.
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.
-
B.
breedingGoal
chosen
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
C.
hasBreedingCode
Indicates that an entity is associated with a specific code representing its breeding status, behavior, or category.
-
D.
breedingProduces
Indicates that a breeding process results in the creation or generation of one or more offspring or new entities.
-
E.
breedingUse
Indicates that one entity is used for breeding or reproductive purposes with respect to another entity.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.