Triple
T15278836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatamá National Natural Park |
E365212
|
entity |
| Predicate | mainBiome |
P952
|
FINISHED |
| Object | tropical montane cloud forest |
—
|
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: tropical montane cloud forest | Statement: [Tatamá National Natural Park, mainBiome, tropical montane cloud forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBiome Context triple: [Tatamá National Natural Park, mainBiome, tropical montane cloud forest]
-
A.
hasSecondaryBiome
Indicates that an entity is associated with an additional, subordinate biome type beyond its primary biome.
-
B.
biome
chosen
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
-
C.
biomeIncludes
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
-
D.
isLocatedInBiome
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
E.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e504d8c8190ad6c565a31d1a9bd |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.