Triple
T20640974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmühl Valley Cycle Route |
E507221
|
entity |
| Predicate | recommendedUseSeason |
P4415
|
FINISHED |
| Object | spring |
—
|
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: spring | Statement: [Altmühl Valley Cycle Route, recommendedUseSeason, spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedUseSeason Context triple: [Altmühl Valley Cycle Route, recommendedUseSeason, spring]
-
A.
usedForSeasonRange
Indicates the span of seasons or time period during which something is intended or suitable to be used.
-
B.
usedInSeason
chosen
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
C.
basedOnSeason
Indicates that something is determined, influenced, or derived according to a particular season or time of year.
-
D.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
E.
seasonalValidity
Indicates that something is valid, applicable, or in effect only during a specific season or set of seasons.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad132ebc8190b557914cf31a9033 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.