Triple
T7399325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Karelia |
E170704
|
entity |
| Predicate | hasMajorRiver |
P165
|
FINISHED |
| Object | Pielisjoki |
E646797
|
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: Pielisjoki | Statement: [North Karelia, hasMajorRiver, Pielisjoki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pielisjoki Context triple: [North Karelia, hasMajorRiver, Pielisjoki]
-
A.
Pielisjoki
chosen
Pielisjoki is a river in eastern Finland that flows from Lake Pielinen through the city of Joensuu toward Lake Pyhäselkä.
-
B.
Pikaliiva
Pikaliiva is a residential subdistrict of Tallinn, Estonia, located within the Haabersti district.
-
C.
Pöytyä
Pöytyä is a rural municipality in southwestern Finland known for its forests, agriculture, and small village communities.
-
D.
Tankavaara
Tankavaara is a small village in Finnish Lapland known for its gold prospecting history and as a gateway to nearby wilderness areas.
-
E.
Pittelo
Pittelo is a residential neighborhood and district within the city of Assen in the province of Drenthe, Netherlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24dbf288190b8dfea455148841b |
completed | March 27, 2026, 9:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c81106c0788190a3740acf7bb4ab86 |
completed | March 28, 2026, 5:33 p.m. |
Created at: March 27, 2026, 3:10 p.m.