Triple
T14387262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sol Duc Road |
E356756
|
entity |
| Predicate | accessesFeatureType |
P101663
|
FINISHED |
| Object | campground |
—
|
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: campground | Statement: [Sol Duc Road, accessesFeatureType, campground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesFeatureType Context triple: [Sol Duc Road, accessesFeatureType, campground]
-
A.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of another entity.
-
B.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
C.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
includesFeatureTypes
chosen
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
E.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90283b9c8190b50d30ad58bfe085 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.