Triple
T30061734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oryza longistaminata |
E763906
|
entity |
| Predicate | traitSourceFor |
P168399
|
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: [Oryza longistaminata, traitSourceFor, disease resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traitSourceFor Context triple: [Oryza longistaminata, traitSourceFor, disease resistance]
-
A.
doctrineSourceFor
Indicates that one entity serves as the originating basis or authoritative source of doctrine, teachings, or principles for another entity.
-
B.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
C.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
D.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
E.
traitStacking
Indicates the combination of multiple traits or characteristics within a single entity or context, typically to achieve a cumulative or enhanced effect.
- F. None of above. chosen
Provenance (4 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca408f88190991b5a628e2834c3 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 6:58 p.m.