Triple
T7280571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom |
E163134
|
entity |
| Predicate | hasSubpeak |
P7612
|
FINISHED |
| Object | Lenzspitze |
E195821
|
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: Lenzspitze | Statement: [Dom, hasSubpeak, Lenzspitze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lenzspitze Context triple: [Dom, hasSubpeak, Lenzspitze]
-
A.
Lenzspitze
chosen
Lenzspitze is a prominent high-altitude peak in the Swiss Pennine Alps, known for its sharp ridges and challenging alpine climbing routes.
-
B.
Gerlachspitze
Gerlachspitze is the highest peak in the High Tatras and in Slovakia, renowned as a prominent alpine climbing and hiking destination in Central Europe.
-
C.
Hochalmspitze
Hochalmspitze is a prominent mountain in the Austrian Alps, renowned for its glaciated summit and challenging alpine climbing routes.
-
D.
Wildspitze
Wildspitze is a prominent mountain in the Ötztal Alps of Tyrol, Austria, known as one of the country's highest and most popular alpine climbing peaks.
-
E.
Birkkarspitze
Birkkarspitze is a prominent Alpine peak in the Karwendel range on the border of Austria and Germany, popular with experienced hikers and mountaineers.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb339b1081909f648864e210f98e |
completed | March 27, 2026, 8:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e532a7f08190a5c0b1167dc0be44 |
completed | March 28, 2026, 2:26 p.m. |
Created at: March 27, 2026, 2:59 p.m.