Triple
T8296813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chetco River |
E194239
|
entity |
| Predicate | hasWildAndScenicDesignation |
P82588
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Chetco River, hasWildAndScenicDesignation, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildAndScenicDesignation Context triple: [Chetco River, hasWildAndScenicDesignation, Yes]
-
A.
stateScenicRiverDesignation
Indicates that a river or river segment has been officially designated by a state as part of its scenic river system or program.
-
B.
designatedAsNationalPark
Indicates that an area has been officially assigned the legal status and protections of a national park by an authorized governing body.
-
C.
hasNationalScenicArea
Indicates that an entity is designated as or associated with a National Scenic Area.
-
D.
designatedWilderness
Indicates that an area has been officially classified and protected as wilderness under a formal designation or legal framework.
-
E.
hasNatureDesignation
Indicates that something has been formally assigned a specific conservation, protection, or natural-area status or designation.
- F. None of above. chosen
Provenance (4 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7df887148190bddc2609bc885cb4 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:53 p.m.