Triple
T20250311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulefoss |
E498533
|
entity |
| Predicate | locatedInMunicipality |
P40
|
FINISHED |
| Object | Nome |
—
|
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: Nome | Statement: [Ulefoss, locatedInMunicipality, Nome]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nome Context triple: [Ulefoss, locatedInMunicipality, Nome]
-
A.
Nome
Nome is a remote coastal city in western Alaska known historically for its gold rush heritage and as a key transportation and supply hub on the Bering Sea.
-
B.
Nome
chosen
Nome is a municipality in southeastern Norway known for its lakes, forests, and the Telemark Canal running through its historic industrial communities.
-
C.
Nom
Nom is a domain name marketplace and service platform operating under the brand Nom.com.
-
D.
Nama
Nama is a Khoe language spoken primarily by the Nama people in Namibia and neighboring regions of southern Africa.
-
E.
Nimi
Nimi is an ancient king in Hindu tradition, often regarded as the first ruler of the Videha kingdom and associated with the lineage of sages and monarchs in Vedic and Puranic texts.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a79a208190a5a7c0f6515bc393 |
completed | April 20, 2026, 6:42 p.m. |
Created at: April 11, 2026, 11:41 p.m.