Triple
T28252838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan River–Great Salt Lake basin |
E712357
|
entity |
| Predicate | isSubbasinOf |
P143391
|
FINISHED |
| Object | Great Basin |
—
|
NE NERFINISHED |
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: Great Basin | Statement: [Jordan River–Great Salt Lake basin, isSubbasinOf, Great Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubbasinOf Context triple: [Jordan River–Great Salt Lake basin, isSubbasinOf, Great Basin]
-
A.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
B.
containsTributariesOf
Indicates that one water body or drainage system includes within it the tributary streams or rivers of another.
-
C.
isPrincipalBasinOf
Indicates that one basin serves as the main or primary drainage basin associated with another geographic or hydrologic feature.
-
D.
basinSubdivision
chosen
Indicates that one basin is a sub-unit or component area within a larger, encompassing basin.
-
E.
isNaturalTributaryOf
Indicates that one watercourse flows naturally into another, contributing its water as a tributary without artificial diversion.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 11:06 p.m.