Triple
T33848186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meursault hillside |
E867538
|
entity |
| Predicate | macroclimate |
P29133
|
FINISHED |
| Object | Burgundian continental climate |
—
|
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: Burgundian continental climate | Statement: [Meursault hillside, macroclimate, Burgundian continental climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: macroclimate Context triple: [Meursault hillside, macroclimate, Burgundian continental climate]
-
A.
climateSubgroup
Indicates that one climate category is a more specific subgroup or subtype within another, broader climate category.
-
B.
climatologicalType
chosen
Indicates the classification of a climate or weather pattern that characterizes a place, period, or condition.
-
C.
climatologicalRegion
Indicates that one entity is a climatological region associated with, or characterizing the climate of, another entity.
-
D.
climatologicalSignificance
Indicates the degree to which something is important, influential, or relevant within the context of climate or long-term weather patterns.
-
E.
climaticRole
Indicates the role or influence that something has on climate patterns or 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700589b148190bb47383469951af6 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.