Triple
T1102492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Floral Region Protected Areas |
E25410
|
entity |
| Predicate | plantSpeciesRichness |
P6211
|
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, plantSpeciesRichness, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantSpeciesRichness Context triple: [Cape Floral Region Protected Areas, plantSpeciesRichness, very high]
-
A.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
B.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
C.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
D.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
E.
hasBotanicalResource
Indicates that an entity possesses, contains, or is associated with a plant-based resource (such as plants, plant parts, or botanical materials) used for some purpose.
- 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.