Triple
T8518891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Fuca Marine Trail |
E201644
|
entity |
| Predicate | hasCampsiteType |
P10334
|
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: [Juan de Fuca Marine Trail, hasCampsiteType, backcountry campsites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampsiteType Context triple: [Juan de Fuca Marine Trail, hasCampsiteType, backcountry campsites]
-
A.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
B.
hasCampingOption
Indicates that an entity offers or includes the possibility to camp (e.g., designated camping facilities or areas).
-
C.
hasCampSites
Indicates that one entity provides, contains, or is associated with one or more designated camping sites for use.
-
D.
hasCampType
chosen
Indicates that an entity is associated with or classified by a particular type or category of camp.
-
E.
hasCampingStyle
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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe627de908190b463da0f26da4ffb |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.