Triple
T37433258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Perennial movement |
E930198
|
entity |
| Predicate | emphasizesPlantTrait |
P126358
|
FINISHED |
| Object | structure |
—
|
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: structure | Statement: [New Perennial movement, emphasizesPlantTrait, structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesPlantTrait Context triple: [New Perennial movement, emphasizesPlantTrait, structure]
-
A.
agronomicTrait
Indicates a relationship where a trait is characterized specifically in terms of its relevance to agricultural growth, management, or productivity of plants or crops.
-
B.
typicalLeafCharacteristic
Indicates the usual or defining features of a leaf that characterize it under normal conditions.
-
C.
flowerCharacteristic
Indicates that a flower possesses a particular attribute, quality, or feature (such as color, shape, size, or scent).
-
D.
botanicalSignificance
Indicates the importance or relevance of one entity to another in a botanical or plant-related context.
-
E.
foliageCharacteristic
chosen
Indicates the specific traits or qualities of an entity’s foliage, such as its type, texture, color, or other distinguishing features.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.