Triple
T14124493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemlocks Reservoir |
E339991
|
entity |
| Predicate | hasRecreationalAspect |
P112901
|
FINISHED |
| Object | scenic views |
—
|
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: scenic views | Statement: [Hemlocks Reservoir, hasRecreationalAspect, scenic views]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalAspect Context triple: [Hemlocks Reservoir, hasRecreationalAspect, scenic views]
-
A.
hasRecreationalContext
Indicates that something occurs, is used, or is understood within a leisure, entertainment, or recreational setting or purpose.
-
B.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
-
C.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
D.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
E.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
- F. None of above. chosen
Provenance (4 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.