Triple
T14188350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Fork American River |
E351640
|
entity |
| Predicate | hasRapidClass |
P66518
|
FINISHED |
| Object | Class 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 III | Statement: [Middle Fork American River, hasRapidClass, Class III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRapidClass Context triple: [Middle Fork American River, hasRapidClass, Class III]
-
A.
hasRapidsClass
chosen
Indicates that a body of water or river segment is assigned a specific rapids difficulty classification.
-
B.
hasRapids
Indicates that a body of water contains sections of fast-flowing, turbulent water known as rapids.
-
C.
containsFast
Indicates that one entity includes or holds another entity in a way that allows rapid or high-speed access, interaction, or processing.
-
D.
isFastGrowing
Indicates that an entity increases in size, quantity, or impact at a rapid or above-average rate over time.
-
E.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61de509881908967ef5031f2a8d9 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:03 a.m.