Triple
T12656448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubartów |
E302295
|
entity |
| Predicate | previousName |
P65
|
FINISHED |
| Object | Lewartów |
E302295
|
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: Lewartów | Statement: [Lubartów, previousName, Lewartów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lewartów Context triple: [Lubartów, previousName, Lewartów]
-
A.
Wojnowo
Wojnowo is a village in western Poland that was formerly known by its German name Reckenwalde.
-
B.
Władysławowo
Władysławowo is a Polish seaside town and popular tourist resort on the Baltic coast, known for its beaches and fishing port.
-
C.
Kozłowo
Kozłowo is a village in northern Poland that serves as an important local center within the Warmian-Masurian Voivodeship.
-
D.
Grodkowo
Grodkowo is a settlement in northern Poland located within the Warmian-Masurian Voivodeship, a region known for its lakes and natural landscapes.
-
E.
Lubartów
chosen
Lubartów is a town in eastern Poland known for its historic architecture and location north of the regional capital Lublin.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961620b188190a8a8569f1133a9cf |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f668832c7081909eb75429efba493e |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:18 p.m.