Triple
T13468333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieprz River |
E311561
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Łęczna |
—
|
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: Łęczna | Statement: [Wieprz River, flowsNear, Łęczna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łęczna Context triple: [Wieprz River, flowsNear, Łęczna]
-
A.
Łęczna
chosen
Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
-
B.
Łęknica
Łęknica is a small town in western Poland near the German border, known for its proximity to the Lusatian Neisse River and the UNESCO-listed Muskau Park.
-
C.
Łęczyca
Łęczyca is a historic town in central Poland known for its medieval castle, role as a regional stronghold of the early Piast dynasty, and significance in the political and religious life of the Polish kingdom.
-
D.
Pszczyna
Pszczyna is a historic town in southern Poland known for its well-preserved castle complex and picturesque 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf21e46081908a00c9acf54f270f |
completed | April 12, 2026, 2:41 p.m. |
Created at: April 9, 2026, 9:42 p.m.