Triple
T23230959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luster |
E581151
|
entity |
| Predicate | hasGlacier |
P4580
|
FINISHED |
| Object | Nigardsbreen |
—
|
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: Nigardsbreen | Statement: [Luster, hasGlacier, Nigardsbreen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nigardsbreen Context triple: [Luster, hasGlacier, Nigardsbreen]
-
A.
Nigardsbreen
chosen
Nigardsbreen is a well-known outlet glacier in Norway, popular for guided glacier walks and as one of the most accessible arms of the Jostedalsbreen ice cap.
-
B.
Jostedalsbreen glacier
Jostedalsbreen glacier is the largest glacier on the European mainland, located in western Norway within Jostedalsbreen National Park.
-
C.
Larsbreen
Larsbreen is a glacier located in Nordenskiöld Land on the Arctic archipelago of Svalbard, Norway.
-
D.
Kjenndalsbreen
Kjenndalsbreen is a scenic outlet glacier in western Norway, known for its dramatic icefalls and accessibility to visitors.
-
E.
Briksdalsbreen glacier arm
Briksdalsbreen glacier arm is a famous and easily accessible outlet glacier in western Norway, known for its dramatic icefall descending into a lush valley that attracts many tourists and hikers.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f19231ef908190a791b4967916a66f |
completed | April 29, 2026, 5:08 a.m. |
Created at: April 17, 2026, 4:09 p.m.