Triple
T18997059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nayki |
E464843
|
entity |
| Predicate | hasSurroundingWaterType |
P29911
|
FINISHED |
| Object | salt lake |
—
|
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: salt lake | Statement: [Nayki, hasSurroundingWaterType, salt lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingWaterType Context triple: [Nayki, hasSurroundingWaterType, salt lake]
-
A.
hasSurroundingWaters
chosen
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
B.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
C.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
D.
hasNearbyWaterBoard
Indicates that an entity is located close to, or within the jurisdictional area of, a water management or water regulatory board.
-
E.
hasAssociatedWaterBody
Indicates that one entity is linked to, or occurs in connection with, a specific body of water such as a river, lake, or sea.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6826464819080ff0e0ffa5cc25e |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.