Triple
T20600755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Haukivesi |
E506170
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Varkaus |
—
|
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: Varkaus | Statement: [Lake Haukivesi, locatedNear, Varkaus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Varkaus Context triple: [Lake Haukivesi, locatedNear, Varkaus]
-
A.
Varkaus
chosen
Varkaus is a small industrial town and municipality in the Northern Savonia region of eastern Finland, known for its paper and wood-processing industries.
-
B.
Vahka
Vahka was a medieval town that served as an early capital of the Armenian Kingdom of Cilicia.
-
C.
Vatutine
Vatutine is a small industrial city in central Ukraine, located within Cherkasy Oblast.
-
D.
Vahetüki
Vahetüki is a small village located in Kiili Parish in northern Estonia.
-
E.
Vitasta
Vitasta is the ancient Sanskrit name for the Jhelum River, a historically significant river of the Kashmir region frequently mentioned in Vedic and classical Indian texts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1ffd088190adeacb9fe4907530 |
completed | April 20, 2026, 10:35 p.m. |
Created at: April 16, 2026, 11:41 a.m.