Triple
T15573255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morning Glory cloud |
E374299
|
entity |
| Predicate | hasPeakMonths |
P108895
|
FINISHED |
| Object | September |
—
|
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: September | Statement: [Morning Glory cloud, hasPeakMonths, September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakMonths Context triple: [Morning Glory cloud, hasPeakMonths, September]
-
A.
isPeakVacationMonthIn
Indicates that a given month falls within the period of highest typical vacation activity in a specified location or context.
-
B.
peakSeasonMonth
chosen
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
-
C.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
D.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
E.
hasLowestFlowMonths
Indicates that the related months are those during which the flow (e.g., of water, traffic, or another quantity) reaches its minimum levels for the given entity or 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2025888190a2b6240296bba13e |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:10 a.m.