Triple
T7706817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galena, Alaska |
E174638
|
entity |
| Predicate | hasMajorRiverFeature |
P165
|
FINISHED |
| Object | seasonal ice breakup on Yukon River |
—
|
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: seasonal ice breakup on Yukon River | Statement: [Galena, Alaska, hasMajorRiverFeature, seasonal ice breakup on Yukon River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRiverFeature Context triple: [Galena, Alaska, hasMajorRiverFeature, seasonal ice breakup on Yukon River]
-
A.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
B.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
D.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
-
E.
hasMajorRiverDelta
Indicates that a geographic region or water body possesses a significant river delta formed by sediment deposition at or near its mouth.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.