Triple
T29583723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Bend Recreation Area |
E753663
|
entity |
| Predicate | isOutdoorRecreationSite |
P167475
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [West Bend Recreation Area, isOutdoorRecreationSite, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOutdoorRecreationSite Context triple: [West Bend Recreation Area, isOutdoorRecreationSite, true]
-
A.
isHikingDestination
Indicates that a location serves as a destination or endpoint for hiking activities or routes.
-
B.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
C.
nationalParkAccess
Indicates that one entity has the right, ability, or permission to enter, use, or benefit from a specified national park.
-
D.
locatedInNationalOrProvincialPark
Indicates that one entity is situated within the boundaries of a national or provincial park.
-
E.
locatedInNationalLakeshore
Indicates that one place or feature is situated within the boundaries of a designated national lakeshore area.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7c7c80819085dc7eae20560af6 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:09 p.m.