Triple
T16211762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spiralia |
E393481
|
entity |
| Predicate | habitatDiversity |
P22357
|
FINISHED |
| Object | marine environments |
—
|
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: marine environments | Statement: [Spiralia, habitatDiversity, marine environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: habitatDiversity Context triple: [Spiralia, habitatDiversity, marine environments]
-
A.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
B.
featuresHabitat
chosen
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
C.
faunaDiversity
Indicates the variety and richness of animal species present within a given area or ecosystem.
-
D.
hasBiodiversitySignificance
Indicates that something possesses ecological importance due to the variety, rarity, or conservation value of the species and habitats it supports.
-
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.