Triple
T35325560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenley Common |
E1020171
|
entity |
| Predicate | hasBiodiversityInterest |
P22447
|
FINISHED |
| Object | butterflies |
—
|
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: butterflies | Statement: [Kenley Common, hasBiodiversityInterest, butterflies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiodiversityInterest Context triple: [Kenley Common, hasBiodiversityInterest, butterflies]
-
A.
hasBotanicalInterest
Indicates that one entity has a particular interest or concern in the botanical characteristics, study, or cultivation of another entity.
-
B.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
C.
hasBiodiversitySignificance
Indicates that something possesses ecological importance due to the variety, rarity, or conservation value of the species and habitats it supports.
-
D.
hasWildlifeFocus
Indicates that something is primarily concerned with, dedicated to, or centered around wildlife.
-
E.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:03 p.m.