Triple
T5036895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feather River Canyon (historic alignment) |
E113446
|
entity |
| Predicate | scenicAttraction |
P33214
|
FINISHED |
| Object | views of Feather River |
—
|
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: views of Feather River | Statement: [Feather River Canyon (historic alignment), scenicAttraction, views of Feather River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenicAttraction Context triple: [Feather River Canyon (historic alignment), scenicAttraction, views of Feather River]
-
A.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
B.
touristAttractionIn
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
C.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
-
D.
sights
Indicates that one entity perceives or observes another entity or object using vision.
-
E.
tourismFeature
chosen
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73bb069c8190af86f1b2f95f3d95 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.