Triple
T4741930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gudbrandsdalen |
E105262
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Otta |
E331809
|
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: Otta | Statement: [Gudbrandsdalen, hasTown, Otta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otta Context triple: [Gudbrandsdalen, hasTown, Otta]
-
A.
Otta
chosen
Otta is a small Norwegian town known as a regional transport hub and gateway to popular mountain and national park areas.
-
B.
Ota
Ota is a historically significant Awori town in southwestern Nigeria that has grown into a major industrial and educational hub.
-
C.
Oppum
Oppum is a district of the German city of Krefeld in the state of North Rhine-Westphalia.
-
D.
Oton
Oton is a coastal municipality in the Philippine province of Iloilo known for its historical heritage and proximity to Iloilo City.
-
E.
Oto
The Oto are a Native American tribe originally from the Great Plains region, historically known for their semi-nomadic lifestyle, agriculture, and participation in 19th-century U.S. treaty negotiations.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a7153881909eac451fc7566d25 |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a28ca648190a44d178826926812 |
completed | March 21, 2026, 6:26 a.m. |
Created at: March 20, 2026, 1:19 p.m.