Triple
T9190205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolno |
E220563
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Kolno@en |
E220563
|
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: Kolno@en | Statement: [Kolno, hasNameInLanguage, Kolno@en]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kolno@en Context triple: [Kolno, hasNameInLanguage, Kolno@en]
-
A.
Kolno
chosen
Kolno is a small town in northeastern Poland known for its rural character and location within the historic Warmia-Masuria area.
-
B.
Kolnes
Kolnes is a village in Karmøy municipality in Rogaland county, southwestern Norway, known for its residential character and proximity to the town of Haugesund.
-
C.
Kol
Kol is a Hebrew surname most notably associated with Moshe Kol, an Israeli politician and one of the signatories of Israel’s Declaration of Independence.
-
D.
Kols
Kols are an indigenous tribal community of central India, primarily residing in the state of Madhya Pradesh and known for their distinct cultural traditions and close association with forest and agrarian livelihoods.
-
E.
Kølpen
Kølpen is one of the small islands in the Hirsholmene archipelago off the northeast coast of Jutland in Denmark.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5bd8c5c81909d0cdbcd7410fcee |
completed | April 1, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c272f508190aade1769c88cf16d |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:24 p.m.