Triple
T29488334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernville, Pennsylvania |
E747993
|
entity |
| Predicate | nearbyRecreationalArea |
P61270
|
FINISHED |
| Object | Blue Marsh Lake |
—
|
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: Blue Marsh Lake | Statement: [Bernville, Pennsylvania, nearbyRecreationalArea, Blue Marsh Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyRecreationalArea Context triple: [Bernville, Pennsylvania, nearbyRecreationalArea, Blue Marsh Lake]
-
A.
hasRecreationalActivityNearby
Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
-
B.
hasRecreationalUseNearby
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
C.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
D.
nearbyActivityHub
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
-
E.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 4:11 p.m.