Triple
T5856974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tropical rain forest |
E130177
|
entity |
| Predicate | canopyClosure |
P29206
|
FINISHED |
| Object | closed 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: closed canopy | Statement: [Tropical rain forest, canopyClosure, closed canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canopyClosure Context triple: [Tropical rain forest, canopyClosure, closed canopy]
-
A.
hasCanopyDensity
Indicates the degree to which a canopy (such as a tree or forest cover) occupies or obscures the area beneath it.
-
B.
hasCanopy
Indicates that one entity possesses or is characterized by a canopy associated with it.
-
C.
canopyPosition
Indicates the relative location or layer an entity occupies within a canopy structure (e.g., upper, middle, or lower canopy).
-
D.
hasTreeCanopyProtection
Indicates that an entity is subject to rules or measures that preserve, limit removal of, or otherwise protect the tree canopy associated with it.
-
E.
forestCoverCharacteristic
chosen
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.