Triple
T21887692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ćwilin |
E540449
|
entity |
| Predicate | hasPolishName |
P15778
|
FINISHED |
| Object | Ćwilin |
—
|
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: Ćwilin | Statement: [Ćwilin, hasPolishName, Ćwilin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ćwilin Context triple: [Ćwilin, hasPolishName, Ćwilin]
-
A.
Ćwilin
chosen
Ćwilin is a prominent mountain peak in southern Poland, known for its panoramic views and popular hiking trails within the Beskid Wyspowy range.
-
B.
Sylwka
Sylwka is a Polish diminutive form of the female given name Sylwia, used as an affectionate or informal nickname.
-
C.
Borówek
Borówek is a small village in central Poland located within the administrative district of Gmina Bielawy.
-
D.
Krowodrza
Krowodrza is a central district of Kraków, Poland, known for its mix of historic urban neighborhoods, academic institutions, and cultural venues.
-
E.
Krupiński
Krupiński is a Polish surname, often borne by individuals of Polish origin and sometimes spelled in variant forms such as Kropinski.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ee5f1c8190b8c6c431039eb8c9 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 16, 2026, 7:05 p.m.