Triple
T23096572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Cross Mountains |
E575906
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Łysica |
—
|
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: Łysica | Statement: [Holy Cross Mountains, hasPeak, Łysica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łysica Context triple: [Holy Cross Mountains, hasPeak, Łysica]
-
A.
Łysica
chosen
Łysica is the highest peak of the Świętokrzyskie (Holy Cross) Mountains in south-central Poland, known for its forested slopes and protected natural environment.
-
B.
Łany
Łany is a village located within the administrative district of Gmina Wojciechowice in south-central Poland.
-
C.
Sylwka
Sylwka is a Polish diminutive form of the female given name Sylwia, used as an affectionate or informal nickname.
-
D.
Ryglice
Ryglice is a small town in southern Poland known for its rural character and location in the historical region of Lesser Poland.
-
E.
Białucha
Białucha is an alternative name for the Prądnik River, a watercourse in southern Poland that flows through the Kraków area.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de522e48190a37e6c2fda2de465 |
completed | April 29, 2026, 4:49 a.m. |
Created at: April 17, 2026, 3:57 p.m.