Triple
T32154978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hosta |
E821258
|
entity |
| Predicate | notableCultivarExamples |
P59038
|
FINISHED |
| Object | Hosta 'Sum and Substance' |
E821258
|
NE 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: Hosta 'Sum and Substance' | Statement: [Hosta, notableCultivarExamples, Hosta 'Sum and Substance']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCultivarExamples Context triple: [Hosta, notableCultivarExamples, Hosta 'Sum and Substance']
-
A.
notableVarieties
chosen
Indicates that there are specific, distinguished types or versions associated with an entity that are recognized as notable.
-
B.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by another entity.
-
C.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
D.
cultivarName
Indicates that a specific cultivated variety (cultivar) is designated by a particular name.
-
E.
exportCultivar
Indicates the action of sending a plant cultivar from one place or organization to another for use, trade, or distribution.
- F. None of above.
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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bcc17108190819daced37bcf89e |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:32 a.m.