Triple
T5754740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Creek (Tuolumne County, California) |
E126937
|
entity |
| Predicate | whitewaterClass |
P17791
|
FINISHED |
| Object | Class V |
—
|
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 V | Statement: [Cherry Creek (Tuolumne County, California), whitewaterClass, Class V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whitewaterClass Context triple: [Cherry Creek (Tuolumne County, California), whitewaterClass, Class V]
-
A.
waterwayClass
chosen
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
B.
typeOfWaterfall
Indicates that one entity is a specific kind or category of waterfall in relation to another entity.
-
C.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
D.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
E.
majorWaterfall
Indicates that a waterfall is of significant size, height, or volume relative to other waterfalls.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02904dcf481909e4340a64ee1034e |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.