Triple
T21178556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potlatch State Park |
E521880
|
entity |
| Predicate | nearestWaterType |
P47449
|
FINISHED |
| Object | saltwater |
—
|
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: saltwater | Statement: [Potlatch State Park, nearestWaterType, saltwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestWaterType Context triple: [Potlatch State Park, nearestWaterType, saltwater]
-
A.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
B.
nearestLargeBodyOfWater
chosen
Indicates the closest significant body of water in proximity to a given location or entity.
-
C.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
D.
nearestCityAcrossWater
Indicates that one city is the closest city to another city when considering only routes or separation across a body of water.
-
E.
nearbyWatercourse
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301b41908190bc104aa748a0346d |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.