Triple
T4566127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dipsea Trail segments |
E121912
|
entity |
| Predicate | peakUseSeason |
P35920
|
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: [Dipsea Trail segments, peakUseSeason, late spring to fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakUseSeason Context triple: [Dipsea Trail segments, peakUseSeason, late spring to fall]
-
A.
peakUse
chosen
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
B.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
C.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
D.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
-
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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589cde9081909b84186d700fc463 |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.