Triple
T6955478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen Am |
E161231
|
entity |
| Predicate | supportsVegetationType |
P34481
|
FINISHED |
| Object | tropical seasonal 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 seasonal forest | Statement: [Köppen Am, supportsVegetationType, tropical seasonal forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVegetationType Context triple: [Köppen Am, supportsVegetationType, tropical seasonal forest]
-
A.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
supportsEcosystemType
chosen
Indicates that one entity provides suitable conditions or resources necessary to sustain or maintain a particular type of ecosystem.
-
D.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
E.
hasVegetationLayer
Indicates that an entity possesses a distinct layer or cover of vegetation as part of its structure or surface.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacf8c8c8190a25dbacebeb4b66e |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.