Triple
T33580692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahtena |
E860139
|
entity |
| Predicate | notableRiverValley |
P40242
|
FINISHED |
| Object | Copper River Valley |
E48701
|
NE 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: Copper River Valley | Statement: [Ahtena, notableRiverValley, Copper River Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRiverValley Context triple: [Ahtena, notableRiverValley, Copper River Valley]
-
A.
hasRiverValley
chosen
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
B.
hasRiverValleyType
Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
-
C.
historicallyAssociatedRiver
Indicates a relationship where an entity has a notable historical connection or association with a particular river, such as through events, development, or cultural significance.
-
D.
ancientNameOfRiver
Indicates that one name is an ancient or historical name used for a particular river.
-
E.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
- F. None of above.
Provenance (4 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36656579308190b35a27f5edaeaafd |
completed | June 20, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.