Triple
T28600786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Lune Valley |
E723903
|
entity |
| Predicate | recreationRoute |
P17835
|
FINISHED |
| Object | Lune Valley walking routes |
—
|
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: Lune Valley walking routes | Statement: [Lower Lune Valley, recreationRoute, Lune Valley walking routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationRoute Context triple: [Lower Lune Valley, recreationRoute, Lune Valley walking routes]
-
A.
hasRecreationalRoute
chosen
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
B.
recreationLocation
Indicates the place where a recreational activity or leisure pursuit occurs.
-
C.
raceRoute
Indicates that one entity serves as the course or path along which a race or competitive event is conducted for another entity.
-
D.
recreationAccessPoint
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
E.
recreationRegion
Indicates that a location or area is designated or used as a region for recreational activities.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:24 a.m.