Triple
T9108017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Submeseta |
E218524
|
entity |
| Predicate | hasSummerCharacteristic |
P43888
|
FINISHED |
| Object | hot summers |
—
|
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: hot summers | Statement: [Northern Submeseta, hasSummerCharacteristic, hot summers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummerCharacteristic Context triple: [Northern Submeseta, hasSummerCharacteristic, hot summers]
-
A.
hasHotSeason
chosen
Indicates that an entity experiences a distinct period of time characterized by hot or high-temperature weather conditions.
-
B.
isSummerOrWinter
Indicates that a given time, date, or season falls within either the summer or winter period, as opposed to other seasons.
-
C.
hasSeasonalStatus
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
D.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
E.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57543448190829853c31e05dd8c |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.