Triple
T18023798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crab Creek coulee |
E431193
|
entity |
| Predicate | surfaceWaterRegime |
P50263
|
FINISHED |
| Object | mostly dry |
—
|
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: mostly dry | Statement: [Crab Creek coulee, surfaceWaterRegime, mostly dry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterRegime Context triple: [Crab Creek coulee, surfaceWaterRegime, mostly dry]
-
A.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
B.
currentHydrology
Indicates the present state or characteristics of water flow, distribution, and related hydrological conditions associated with an entity.
-
C.
hasHydrologicalRegime
chosen
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
D.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
E.
surfaceWaterOutlet
Indicates a relationship where surface water from one location flows out or is discharged through a specific outlet or exit point.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c475dc819086c4cd86d663791f |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.