Triple
T3828616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namib sand gecko |
E88752
|
entity |
| Predicate | waterConservation |
P31699
|
FINISHED |
| Object | adapted to low water availability |
—
|
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: adapted to low water availability | Statement: [Namib sand gecko, waterConservation, adapted to low water availability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterConservation Context triple: [Namib sand gecko, waterConservation, adapted to low water availability]
-
A.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
B.
homeWater
Indicates that an entity supplies or uses water within a home or household context.
-
C.
waterQualityUse
Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
-
D.
waterQualityProtection
Indicates efforts, measures, or responsibilities aimed at preserving or improving the cleanliness, safety, and ecological integrity of water resources.
-
E.
conservation
chosen
Indicates the preservation, protection, or careful management of a resource, system, or quantity so that it is maintained over time without depletion or loss.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.