Triple
T14225461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praga |
E352605
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Szmulowizna |
E905828
|
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: Szmulowizna | Statement: [Praga, hasPart, Szmulowizna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Szmulowizna Context triple: [Praga, hasPart, Szmulowizna]
-
A.
Szmulowizna
chosen
Szmulowizna is a historic residential neighborhood in Warsaw, Poland, located within the Praga-Północ district on the eastern bank of the Vistula River.
-
B.
Kruszewnia
Kruszewnia is a village in western Poland notable as the birthplace of German World War I general Erich Ludendorff.
-
C.
Zarzecze
Zarzecze is a village in southeastern Poland historically associated with Polish statesman Aleksander Skrzyński, who maintained a residence there.
-
D.
Redłowo
Redłowo is a coastal district of the Polish city of Gdynia, known for its residential character and proximity to the Baltic Sea.
-
E.
Sadowie
Sadowie is a village and the seat of a rural administrative district in south-eastern Poland.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6228e53c8190abbe4e2d88a7362a |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd281611b48190b787e38ba9c733a4 |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 10, 2026, 1:06 a.m.