Triple
T38108738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Colony |
E951592
|
entity |
| Predicate | climateSystem |
P2043
|
FINISHED |
| Object | Köppen climate classification |
—
|
NE NERFINISHED |
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: Köppen climate classification | Statement: [Frontier Colony, climateSystem, Köppen climate classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateSystem Context triple: [Frontier Colony, climateSystem, Köppen climate classification]
-
A.
climateModel
Indicates a relationship where an entity functions as or is associated with a model used to simulate or predict climate behavior and changes.
-
B.
hasClimateSystem
chosen
Indicates that one entity possesses or is characterized by a particular climate system.
-
C.
climateDriver
Indicates a factor or process that significantly influences or drives changes in climate conditions.
-
D.
climate
Indicates a relationship where environmental or atmospheric conditions influence, shape, or characterize something (such as a place, system, or process).
-
E.
climateProxy
Indicates a relationship where one entity serves as an indirect measure or substitute used to infer the climatic conditions affecting another entity or time period.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.