Triple
T3493423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapland |
E73789
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Inari |
E316364
|
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: Inari | Statement: [Lapland, contains, Inari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inari Context triple: [Lapland, contains, Inari]
-
A.
Inari
Inari is a major Shinto kami associated primarily with rice, agriculture, prosperity, and fox spirits in Japan.
-
B.
Tikkakoski
Tikkakoski is a district in Jyväskylä, Finland, known for its military air base and role as a key center for the Finnish Air Force.
-
C.
Inari municipality
chosen
Inari municipality is a large, sparsely populated municipality in northern Finnish Lapland known for its rich Sámi culture, extensive wilderness areas, and numerous lakes.
-
D.
Taipale
Taipale is a locality in Finland historically notable as a major battleground during the Winter War between Finland and the Soviet Union.
-
E.
Raisio
Raisio is a town and municipality in southwestern Finland known for its industrial base and as the headquarters of the food company Raisio Group.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbad51648190b756ad621d6d7df0 |
completed | March 8, 2026, 6:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b373c23b188190a927d793b03192dc |
completed | March 13, 2026, 2:17 a.m. |
Created at: March 8, 2026, 3:18 p.m.