Triple
T21263672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łysa Góra |
E524068
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Łysiec |
—
|
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: Łysiec | Statement: [Łysa Góra, hasAlternativeName, Łysiec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łysiec Context triple: [Łysa Góra, hasAlternativeName, Łysiec]
-
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.
Łęczna
Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
-
C.
Luborzyca
Luborzyca is a village in southern Poland that serves as the administrative center of the Gmina Kocmyrzów-Luborzyca in Lesser Poland Voivodeship.
-
D.
Oleśnica
Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
-
E.
Oleśnica
Oleśnica is a village located in Busko County in the Świętokrzyskie Voivodeship of south-central Poland.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e9b2788190b834ba38367fb6c7 |
completed | April 21, 2026, 8:31 a.m. |
Created at: April 16, 2026, 4 p.m.