Triple
T29206686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heliosciurus |
E740429
|
entity |
| Predicate | usesMicrohabitat |
P96824
|
FINISHED |
| Object | tree canopy |
—
|
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: tree canopy | Statement: [Heliosciurus, usesMicrohabitat, tree canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMicrohabitat Context triple: [Heliosciurus, usesMicrohabitat, tree canopy]
-
A.
microhabitat
Indicates a specific, localized habitat or environmental niche within a larger habitat where an organism lives or an interaction occurs.
-
B.
usesHabitatFeature
chosen
Indicates that an organism makes use of a particular habitat feature (such as a structure, resource, or microhabitat) as part of its behavior or life history.
-
C.
hasMicroclimateFunction
Indicates that something performs or contributes to a specific microclimate-regulating role or effect within an environment.
-
D.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
E.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 12:09 p.m.