Triple
T28252816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan River–Great Salt Lake basin |
E712357
|
entity |
| Predicate | primaryTerminalWaterBody |
P1778
|
FINISHED |
| Object | Great Salt Lake |
—
|
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 Salt Lake | Statement: [Jordan River–Great Salt Lake basin, primaryTerminalWaterBody, Great Salt Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTerminalWaterBody Context triple: [Jordan River–Great Salt Lake basin, primaryTerminalWaterBody, Great Salt Lake]
-
A.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
B.
bodyOfWater
chosen
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
landingBodyOfWater
Indicates that an entity (such as an aircraft or vessel) lands on or comes to rest upon a specified body of water.
-
D.
namedWaterBody
Indicates that an entity is identified as a specific water body by a given name.
-
E.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
- 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_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: April 27, 2026, 11:06 p.m.