Triple
T11783906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Płońsk County |
E280219
|
entity |
| Predicate | hasRuralGmina |
P46876
|
FINISHED |
| Object | Załuski |
E957574
|
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: Załuski | Statement: [Płońsk County, hasRuralGmina, Załuski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Załuski Context triple: [Płońsk County, hasRuralGmina, Załuski]
-
A.
Załuski
chosen
Załuski is a village in east-central Poland that serves as the seat of the rural administrative district Gmina Załuski in Płońsk County, Masovian Voivodeship.
-
B.
Załęski
Załęski is a Polish surname, a diacritic variant of Zaleski, borne by individuals and families of Polish origin.
-
C.
Zbyszko
Zbyszko is a Polish given name, traditionally used as a diminutive or variant of Zbigniew and known from medieval and literary contexts.
-
D.
Szczawnica
Szczawnica is a Polish spa and tourist town in southern Lesser Poland, known for its mineral springs, health resorts, and scenic location in the Pieniny region near the Dunajec River.
-
E.
Łę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.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a585795c8190aa8a5edf0d99b47f |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48a1d244c81908628b01afe467023 |
completed | May 1, 2026, 11:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.