Triple
T25251803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onota Lake |
E632758
|
entity |
| Predicate | isPopularTouristDestinationIn |
P158315
|
FINISHED |
| Object | Berkshires |
—
|
NE NERFINISHED |
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: Berkshires | Statement: [Onota Lake, isPopularTouristDestinationIn, Berkshires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularTouristDestinationIn Context triple: [Onota Lake, isPopularTouristDestinationIn, Berkshires]
-
A.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
B.
areMajorTouristDestinations
Indicates that the referenced places are widely recognized and frequently visited as primary tourist destinations.
-
C.
alsoAttractsTouristsIn
Indicates that a place, in addition to another, draws or appeals to tourists within a specified location or context.
-
D.
majorTouristDestinationSince
Indicates that a place has been widely recognized and frequented as a major tourist destination starting from a specified point in time.
-
E.
isMajorAttractionIn
Indicates that something is a primary or highly significant attraction within a particular place or location.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808b8ab08190b48cca8408c88bdf |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:11 p.m.