Triple
T14245746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Garden (Olbrich Botanical Gardens) |
E353127
|
entity |
| Predicate | usesPlantingStyle |
P9738
|
FINISHED |
| Object | alpine planting |
—
|
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: alpine planting | Statement: [Rock Garden (Olbrich Botanical Gardens), usesPlantingStyle, alpine planting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlantingStyle Context triple: [Rock Garden (Olbrich Botanical Gardens), usesPlantingStyle, alpine planting]
-
A.
plantingStyle
chosen
Indicates the method or arrangement used to plant entities in relation to each other or their environment.
-
B.
agriculturalPractice
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
C.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
D.
plantedIn
Indicates that one entity has been placed or sown into another entity as its growing or containing medium.
-
E.
plantUse
Indicates that a plant is used for a particular purpose, function, or application.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de629464f88190817b190731bab156 |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.