Triple
T7562953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petersburg, West Virginia |
E178837
|
entity |
| Predicate | hasNearbyOutdoorRecreation |
P68166
|
FINISHED |
| Object | hiking |
—
|
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: hiking | Statement: [Petersburg, West Virginia, hasNearbyOutdoorRecreation, hiking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyOutdoorRecreation Context triple: [Petersburg, West Virginia, hasNearbyOutdoorRecreation, hiking]
-
A.
hasRecreationalUseNearby
chosen
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
B.
hasNearbyStatePark
Indicates that a location is situated close to at least one designated state park.
-
C.
hasNearbyGreenSpace
Indicates that an entity is located close to an area of green space, such as a park, garden, or natural vegetation.
-
D.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
E.
hasNearbyProvincialPark
Indicates that one entity is located close to, or in the vicinity of, a provincial park.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8f994a48190b8338654d6777654 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.