Triple
T24356993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Ynez Valley Botanic Garden |
E613949
|
entity |
| Predicate | plantTypeShowcased |
P36488
|
FINISHED |
| Object | California native plants |
—
|
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: California native plants | Statement: [Santa Ynez Valley Botanic Garden, plantTypeShowcased, California native plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantTypeShowcased Context triple: [Santa Ynez Valley Botanic Garden, plantTypeShowcased, California native plants]
-
A.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
B.
plantCollection
chosen
Indicates that one entity maintains or possesses a collection of plants, typically grouped or curated as a set.
-
C.
examplePlant
Indicates that one entity serves as an illustrative or representative plant instance for another entity or context.
-
D.
plantName
Indicates that the associated value is the name or designated label of a plant.
-
E.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.