Triple
T15088223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geraniales |
E360339
|
entity |
| Predicate | includesOrnamentalGenus |
P13243
|
FINISHED |
| Object | Geranium |
—
|
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: Geranium | Statement: [Geraniales, includesOrnamentalGenus, Geranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOrnamentalGenus Context triple: [Geraniales, includesOrnamentalGenus, Geranium]
-
A.
includesOrnamentalPlant
chosen
Indicates that one entity contains, features, or has as part of it an ornamental plant used primarily for decorative purposes.
-
B.
genusIncludes
Indicates that a particular genus contains or encompasses the specified subordinate taxonomic entities (such as species or subspecies).
-
C.
ornamentalVariety
Indicates that one entity is a decorative or ornamental variety or form of another entity.
-
D.
isOrnamentalPlant
Indicates that a plant is primarily grown or used for decorative or aesthetic purposes rather than for food, medicine, or other practical uses.
-
E.
notableOrnamental
Indicates that something is recognized as a particularly significant or distinguished example of ornamental decoration or design.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:03 a.m.