Triple
T12386226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrus betulifolia |
E295870
|
entity |
| Predicate | rootstockTrait |
P100083
|
FINISHED |
| Object | vigorous growth |
—
|
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: vigorous growth | Statement: [Pyrus betulifolia, rootstockTrait, vigorous growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rootstockTrait Context triple: [Pyrus betulifolia, rootstockTrait, vigorous growth]
-
A.
rootstockOftenGraftedOnto
Indicates that one plant or tree is frequently used as the rootstock onto which another plant or tree is grafted.
-
B.
rootSystemCharacteristic
chosen
Indicates a relationship where a specified characteristic or property is attributed to the root system of an organism or plant.
-
C.
stemType
Indicates the type or form of a stem that an entity possesses or is characterized by.
-
D.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
E.
rhizoidType
Indicates the specific kind or category of rhizoid structure associated with an organism or anatomical feature.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbd489c819098233a111442762e |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.