Triple
T13239951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nashoba Valley Ski Area |
E315253
|
entity |
| Predicate | nearbyAttractionFor |
P3449
|
FINISHED |
| Object | local communities |
—
|
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: local communities | Statement: [Nashoba Valley Ski Area, nearbyAttractionFor, local communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAttractionFor Context triple: [Nashoba Valley Ski Area, nearbyAttractionFor, local communities]
-
A.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
D.
nearbyActivity
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
E.
hasAttractionNearby
chosen
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5850ac8190849a51da39efe5be |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.