Triple
T8615453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Grove area of Kings Canyon National Park |
E204023
|
entity |
| Predicate | typicalSeasonOpen |
P13215
|
FINISHED |
| Object | late spring to fall |
—
|
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: late spring to fall | Statement: [Cedar Grove area of Kings Canyon National Park, typicalSeasonOpen, late spring to fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSeasonOpen Context triple: [Cedar Grove area of Kings Canyon National Park, typicalSeasonOpen, late spring to fall]
-
A.
typicalSeasonTiming
chosen
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
B.
typicalStartSeason
Indicates the season during which something (such as an activity, event, or phenomenon) usually begins.
-
C.
seasonOpeningOrClosing
Indicates that an event marks either the beginning or the end of a particular season.
-
D.
seasonTypicalStartMonth
Indicates the calendar month in which a particular season usually begins.
-
E.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc47020748819090f658c115c1a7b9 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.