Triple
T13815444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki region |
E332002
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Inkoo |
E989255
|
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: Inkoo | Statement: [Helsinki region, contains, Inkoo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inkoo Context triple: [Helsinki region, contains, Inkoo]
-
A.
Inkoo
chosen
Inkoo is a coastal municipality in southern Finland known for its bilingual Finnish-Swedish community and location along the Gulf of Finland.
-
B.
Injinoo
Injinoo is a remote Indigenous community in far northern Queensland, Australia, located on the Cape York Peninsula.
-
C.
Inkeri
Inkeri refers to the Ingrian Finns, a Finnic ethnic group historically inhabiting the Ingria region near Saint Petersburg in northwestern Russia.
-
D.
Jinki
Jinki was a Japanese era name (nengō) of the Nara period, used during the reign of Empress Genshō.
-
E.
Sijjin
Sijjin is an Islamic term referring to a record or register in which the deeds of the wicked are inscribed and a place associated with severe punishment in the Hereafter.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8e0112481909deb31f8614f8b93 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.