Triple
T21688263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southgate River basin |
E535288
|
entity |
| Predicate | surfaceWaterType |
P1011
|
FINISHED |
| Object | mountain river system |
—
|
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: mountain river system | Statement: [Southgate River basin, surfaceWaterType, mountain river system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceWaterType Context triple: [Southgate River basin, surfaceWaterType, mountain river system]
-
A.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
B.
waterbodyType
chosen
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
C.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
D.
surfaceWaterOutlet
Indicates a relationship where surface water from one location flows out or is discharged through a specific outlet or exit point.
-
E.
waterBodyTypeUpstream
Indicates that one water body is of a specified type and is located upstream relative to another water body or reference 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cd51d481908df67e4f69826b06 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.