Triple
T4957213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork American River |
E111313
|
entity |
| Predicate | difficultyClassRange |
P59671
|
FINISHED |
| Object | Class II–III |
—
|
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: Class II–III | Statement: [South Fork American River, difficultyClassRange, Class II–III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: difficultyClassRange Context triple: [South Fork American River, difficultyClassRange, Class II–III]
-
A.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
B.
difficultyRelativeTo
Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
-
C.
difficultyGradingContext
Indicates the contextual factors or conditions that influence how difficult it is to assign a grade or evaluation to something.
-
D.
gradeRange
Indicates the span of grades or scores that an item, performance, or entity falls within.
-
E.
difficultySystem
Indicates a relationship where a system is characterized or classified by its level of difficulty.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6d98dc88819083459a01d3e8fc45 |
completed | March 20, 2026, 3:54 p.m. |
Created at: March 20, 2026, 1:32 p.m.