Triple
T14612467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rysy hiking route |
E342994
|
entity |
| Predicate | leadsTo |
P37
|
FINISHED |
| Object | Rysy |
E69209
|
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: Rysy | Statement: [Rysy hiking route, leadsTo, Rysy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rysy Context triple: [Rysy hiking route, leadsTo, Rysy]
-
A.
Rysy
chosen
Rysy is a prominent peak in the High Tatras on the border of Poland and Slovakia, popular with hikers for its panoramic alpine views and status as Poland’s highest summit.
-
B.
Roztocze
Roztocze is a picturesque upland region spanning southeastern Poland and western Ukraine, known for its rolling hills, forests, and protected natural landscapes.
-
C.
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.
-
D.
Wielki Szyszak
Wielki Szyszak is one of the highest and most prominent mountain peaks in the Karkonosze range on the Polish–Czech border.
-
E.
Ornytion
Ornytion is a minor figure in Greek mythology, traditionally known as a son of the Corinthian king Sisyphus and father of Merope.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb450e6588190a94488d8e71888c8 |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde16c005c81908b54fcfd4243d820 |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:25 a.m.