Triple
T13468337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieprz River |
E311561
|
entity |
| Predicate | nameInPolish |
P15778
|
FINISHED |
| Object | Wieprz |
E722768
|
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: Wieprz | Statement: [Wieprz River, nameInPolish, Wieprz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wieprz Context triple: [Wieprz River, nameInPolish, Wieprz]
-
A.
Wieprz
chosen
Wieprz is a river in eastern Poland that flows through the Lublin region before joining the Western Bug.
-
B.
Wieprz
Wieprz is a village located in southern Poland within the administrative region of Wadowice County in Lesser Poland Voivodeship.
-
C.
Gąsawka
Gąsawka is a river in north-central Poland that flows through the Kuyavian-Pomeranian region before joining the Noteć River.
-
D.
Wieprzec
Wieprzec is a village in southern Poland located within the administrative district of Gmina Maków Podhalański in Lesser Poland Voivodeship.
-
E.
Kurzętnik
Kurzętnik is a village in northern Poland known for its historical character and location within the picturesque Warmian-Masurian region.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf21e46081908a00c9acf54f270f |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74629f1408190b54194fe794be39a |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:42 p.m.