Triple
T18380806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giswil |
E446436
|
entity |
| Predicate | neighboringMunicipality |
P17964
|
FINISHED |
| Object | Kerns |
—
|
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: Kerns | Statement: [Giswil, neighboringMunicipality, Kerns]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kerns Context triple: [Giswil, neighboringMunicipality, Kerns]
-
A.
Kerns
Kerns is a mixed residential and commercial neighborhood in inner east Portland, Oregon, known for its historic homes, local eateries, and proximity to downtown.
-
B.
Kerns
chosen
Kerns is a Swiss municipality in the canton of Obwalden known for its rural alpine landscape and traditional Central Swiss character.
-
C.
Kerns
Kerns is a surname most notably associated with American actress and television director Joanna Kerns.
-
D.
Karns
Karns is an unincorporated suburban community in Knox County, Tennessee, situated within the Knoxville metropolitan area.
-
E.
Kern
Kern is a surname most famously associated with Jerome Kern, the pioneering American composer of early 20th-century musical theatre and popular song.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179aa328819097f5ed8193cfa401 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 10:45 a.m.