Triple
T37433255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Perennial movement |
E930198
|
entity |
| Predicate | emphasizesPlantType |
P4282
|
FINISHED |
| Object | perennial plants |
—
|
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: perennial plants | Statement: [New Perennial movement, emphasizesPlantType, perennial plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesPlantType Context triple: [New Perennial movement, emphasizesPlantType, perennial plants]
-
A.
hostPlantType
Indicates the type or category of plant that serves as a host for another organism (such as an insect, fungus, or parasite).
-
B.
plantType
chosen
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
D.
examplePlant
Indicates that one entity serves as an illustrative or representative plant instance for another entity or context.
-
E.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.