Triple
T6117685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abes and Essens Lake Trail |
E136400
|
entity |
| Predicate | hasCampsites |
P50042
|
FINISHED |
| Object | backcountry campsites |
—
|
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: backcountry campsites | Statement: [Abes and Essens Lake Trail, hasCampsites, backcountry campsites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampsites Context triple: [Abes and Essens Lake Trail, hasCampsites, backcountry campsites]
-
A.
hasNumberOfCampsites
Indicates the specific quantity of campsites associated with a given place, facility, or area.
-
B.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
C.
trainingCampSite
Indicates that a location serves as the site where training camps are held or conducted.
-
D.
hasCampingPolicy
Indicates that an entity specifies rules, restrictions, or guidelines regarding camping activities on its premises or within its jurisdiction.
-
E.
hasCampingStyle
chosen
Indicates that an entity is associated with a particular style or manner of camping.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bec9b8c8190b3268b0ba952aae6 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.