Triple
T23660137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unalaska |
E584419
|
entity |
| Predicate | nearestMajorWaterway |
P47449
|
FINISHED |
| Object | Unalaska Bay |
—
|
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: Unalaska Bay | Statement: [Unalaska, nearestMajorWaterway, Unalaska Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorWaterway Context triple: [Unalaska, nearestMajorWaterway, Unalaska Bay]
-
A.
nearestLargeBodyOfWater
chosen
Indicates the closest significant body of water in proximity to a given location or entity.
-
B.
nearestCityAcrossWater
Indicates that one city is the closest city to another city when considering only routes or separation across a body of water.
-
C.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
D.
nearestMainlandPoint
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35f03448190834991c2a65ef0e4 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.