Triple
T14011952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Beskids |
E337102
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Łamana Skała |
E317994
|
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: Łamana Skała | Statement: [Little Beskids, hasPeak, Łamana Skała]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łamana Skała Context triple: [Little Beskids, hasPeak, Łamana Skała]
-
A.
Łamana Skała
chosen
Łamana Skała is a mountain peak in the Maków Beskids range in southern Poland, known for its rocky summit and scenic hiking routes.
-
B.
Skała
Skała is a small historic town in southern Poland, located near Kraków and known as a gateway to the scenic Ojców National Park.
-
C.
Płaska Skała
Płaska Skała is one of the notable peaks within the Trzy Korony massif in the Pieniny Mountains of southern Poland.
-
D.
Teplické skály
Teplické skály is a renowned sandstone rock formation and popular hiking and climbing area in northeastern Bohemia, Czech Republic, forming part of the larger Adršpach-Teplice Rocks nature reserve.
-
E.
Wysokie Skałki
Wysokie Skałki is the highest peak of the Pieniny range in southern Poland, known for its scenic views and popular hiking trails.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed5cfd0819085b9c860b119a9de |
completed | April 14, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbacaa16e88190995fd86951fb54e6 |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:19 p.m.