Triple
T17059841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Podgórze Market Square |
E413926
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Podgórze |
—
|
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: Podgórze | Statement: [Podgórze Market Square, locatedIn, Podgórze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Podgórze Context triple: [Podgórze Market Square, locatedIn, Podgórze]
-
A.
Podgórze
chosen
Podgórze is a district of Kraków, Poland, historically known for its Jewish ghetto during World War II and its proximity to the former Płaszów concentration camp.
-
B.
Zagórze
Zagórze is a cultural subregion within Poland’s Podtatrze area, known for its distinct local traditions and highland heritage.
-
C.
Grochów
Grochów is a historic residential district in the Praga-Południe area of Warsaw, Poland, known for its pre-war architecture and role in the city’s industrial and working-class heritage.
-
D.
Zagórzyce
Zagórzyce is a village in southeastern Poland located within the administrative district of Gmina Tuszów Narodowy.
-
E.
Grochowe
Grochowe is a village in southeastern Poland located within the administrative district of Gmina Tuszów Narodowy in the Subcarpathian region.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3db7c21a881909bfb67080706612f |
completed | April 18, 2026, 7:29 p.m. |
Created at: April 10, 2026, 5:34 a.m.