Triple
T36072604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelargonium |
E1043405
|
entity |
| Predicate | notableHorticulturalGroup |
P68098
|
FINISHED |
| Object | zonal pelargoniums |
—
|
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: zonal pelargoniums | Statement: [Pelargonium, notableHorticulturalGroup, zonal pelargoniums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHorticulturalGroup Context triple: [Pelargonium, notableHorticulturalGroup, zonal pelargoniums]
-
A.
notablePrincipalHorticulturalist
Indicates that someone is recognized as a principal (leading or head) horticulturalist associated with a particular entity or context.
-
B.
hasFloraGroup
chosen
Indicates that an entity is associated with, contains, or is characterized by a particular group or category of plant life.
-
C.
notableArchitectGroup
Indicates that the subject is a group of architects recognized for their significant or distinguished contributions.
-
D.
notableUserGroup
Indicates that the subject is associated with a user group that is distinguished or recognized as notable in some specific context.
-
E.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.