Triple
T15175494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghent, West Virginia |
E362597
|
entity |
| Predicate | hasOutdoorRecreationNearby |
P68166
|
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: [Ghent, West Virginia, hasOutdoorRecreationNearby, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutdoorRecreationNearby Context triple: [Ghent, West Virginia, hasOutdoorRecreationNearby, true]
-
A.
hasRecreationalUseNearby
chosen
Indicates that there is at least one location or facility for recreational activities situated close to the referenced entity.
-
B.
hasOutdoorResource
Indicates that an entity is associated with, provides, or includes access to an outdoor resource or facility.
-
C.
locatedNearNationalPark
Indicates that one place or entity is situated in close proximity to a national park.
-
D.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
E.
hasNearbyAreaOfOutstandingNaturalBeauty
Indicates that an entity is located close to an officially designated Area of Outstanding Natural Beauty.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0066236d481909e8ac47f496861ad |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.