Triple
T9456959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pohnpei Island highlands |
E228039
|
entity |
| Predicate | microclimate |
P2900
|
FINISHED |
| Object | frequent cloud cover |
—
|
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: frequent cloud cover | Statement: [Pohnpei Island highlands, microclimate, frequent cloud cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: microclimate Context triple: [Pohnpei Island highlands, microclimate, frequent cloud cover]
-
A.
microhabitat
Indicates a specific, localized habitat or environmental niche within a larger habitat where an organism lives or an interaction occurs.
-
B.
preferredClimate
Indicates the type of climate that an entity favors or is most suited to.
-
C.
nativeToClimate
Indicates that an entity naturally originates from or is originally adapted to a specified climate or climatic region.
-
D.
environmentalCondition
chosen
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
E.
climateDependent
Indicates that the existence, behavior, or outcome of something is determined or significantly influenced by climatic conditions.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f90cf648190ab238ba6b4f03c4f |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.