Triple
T30854571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köppen Cfa |
E785883
|
entity |
| Predicate | isCommonInHemisphere |
P1889
|
FINISHED |
| Object | Northern Hemisphere |
—
|
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: Northern Hemisphere | Statement: [Köppen Cfa, isCommonInHemisphere, Northern Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonInHemisphere Context triple: [Köppen Cfa, isCommonInHemisphere, Northern Hemisphere]
-
A.
isInNorthernCelestialHemisphere
Indicates that an astronomical object’s position lies north of the celestial equator in the northern half of the sky.
-
B.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
C.
hemispherePresence
chosen
Indicates the spatial relationship of whether and in which hemisphere(s) (e.g., northern, southern, eastern, western) an entity is present or occurs.
-
D.
hasProgenyInHemisphere
Indicates that an entity has offspring or descendants located within a specified hemisphere.
-
E.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:46 p.m.