Triple
T9288011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benmore Botanic Garden |
E223445
|
entity |
| Predicate | hasPlantDiversity |
P22447
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Benmore Botanic Garden, hasPlantDiversity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlantDiversity Context triple: [Benmore Botanic Garden, hasPlantDiversity, high]
-
A.
hasPlantOriginDiversity
Indicates that something exhibits a variety of origins or sources specifically related to plants or plant-based materials.
-
B.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
C.
hasDiverseLandscape
Indicates that an entity possesses a variety of distinct physical or environmental features within its geographic area.
-
D.
hasBiodiversitySignificance
Indicates that something possesses ecological importance due to the variety, rarity, or conservation value of the species and habitats it supports.
-
E.
hasMajorPlant
Indicates that one entity possesses or hosts a primary or most significant plant facility or installation in relation to another entity.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0861425c81909e3ab11e19cc2f65 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.