Triple
T19560157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gash River |
E489426
|
entity |
| Predicate | dischargePattern |
P89064
|
FINISHED |
| Object | highly seasonal flow |
—
|
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: highly seasonal flow | Statement: [Gash River, dischargePattern, highly seasonal flow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dischargePattern Context triple: [Gash River, dischargePattern, highly seasonal flow]
-
A.
dischargeType
Indicates the manner or category of how something is released, emitted, or discharged from a source.
-
B.
dischargePath
Indicates the route or channel through which a substance, energy, or fluid is released or discharged from its source to its destination.
-
C.
dischargeStatus
Indicates the current state or outcome of an entity’s release or discharge from a prior condition, process, or obligation.
-
D.
dischargesFrom
Indicates that something (such as a fluid, substance, or energy) flows or is released out of a specified source or origin.
-
E.
dischargeVariation
chosen
Indicates a change or difference in the amount, rate, or pattern of discharge (such as flow, emission, or release) between two states, times, or conditions.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f731ae48190ade295c15db7f8ed |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.