Triple
T2188345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groundcover Collection |
E49802
|
entity |
| Predicate | typeOfPlantsIncluded |
P4282
|
FINISHED |
| Object | ornamental groundcovers |
—
|
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: ornamental groundcovers | Statement: [Groundcover Collection, typeOfPlantsIncluded, ornamental groundcovers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPlantsIncluded Context triple: [Groundcover Collection, typeOfPlantsIncluded, ornamental groundcovers]
-
A.
plantType
chosen
Indicates the specific kind or category of plant that an entity is classified as.
-
B.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
C.
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).
-
D.
includesOrnamentalPlant
Indicates that one entity contains, features, or has as part of it an ornamental plant used primarily for decorative purposes.
-
E.
hasPlantSymbol
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.