Triple
T1102496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Floral Region Protected Areas |
E25410
|
entity |
| Predicate | endemicSpeciesConcentration |
P8223
|
FINISHED |
| Object | very 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: very high | Statement: [Cape Floral Region Protected Areas, endemicSpeciesConcentration, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endemicSpeciesConcentration Context triple: [Cape Floral Region Protected Areas, endemicSpeciesConcentration, very high]
-
A.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
hasEndemismLevel
chosen
Indicates the degree to which something is restricted or native to a particular geographic area or region.
-
C.
numberOfSpecies
Indicates the count of distinct species associated with a given entity or context.
-
D.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
E.
biodiversityStatus
Indicates the current condition or level of biological diversity associated with an entity, often in terms of richness, health, or conservation concern.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c21c2c8190a34d91a7afed23a9 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b7472c848190b0643872f67084a2 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.