Triple
T19110930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympus UNESCO Biosphere Reserve |
E467785
|
entity |
| Predicate | floraDiversity |
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: [Olympus UNESCO Biosphere Reserve, floraDiversity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floraDiversity Context triple: [Olympus UNESCO Biosphere Reserve, floraDiversity, high]
-
A.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
B.
studiedFloraOf
Indicates that a subject conducted research or examination on the plant life (flora) of a specified object or region.
-
C.
faunaDiversity
Indicates the variety and richness of animal species present within a given area or ecosystem.
-
D.
shareBiodiversityFeature
Indicates that two or more entities have a biodiversity-related characteristic, attribute, or feature in common.
-
E.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e393bafc81908e35a0eba7b807a6 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.