Triple
T580531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirachmaceae |
E15045
|
entity |
| Predicate | speciesRichness |
P1676
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Dirachmaceae, speciesRichness, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesRichness Context triple: [Dirachmaceae, speciesRichness, low]
-
A.
biodiversityStatus
chosen
Indicates the current condition or level of biological diversity associated with an entity, often in terms of richness, health, or conservation concern.
-
B.
numberOfSpecies
Indicates the count of distinct species associated with a given entity or context.
-
C.
biodiversityHotspot
Indicates a location or region that supports exceptionally high levels of biodiversity, often with many endemic or threatened species, and is therefore considered a conservation priority.
-
D.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
E.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b82b5248190ac863407e8207a3b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.