Triple
T22084063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Garden |
E545725
|
entity |
| Predicate | notablePlantColorRestriction |
P4578
|
FINISHED |
| Object | exclusively white flowers |
—
|
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: exclusively white flowers | Statement: [White Garden, notablePlantColorRestriction, exclusively white flowers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlantColorRestriction Context triple: [White Garden, notablePlantColorRestriction, exclusively white flowers]
-
A.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
B.
hasFlowerColor
chosen
Indicates that an entity (typically a plant or flower) possesses a specific flower color.
-
C.
leafColor
Indicates the color or coloration characteristics of a leaf in relation to a plant or plant part.
-
D.
containsPlantsWith
Indicates that one entity includes or holds within it one or more plant entities.
-
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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b95e908190bd846f531eb59b50 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:28 p.m.