Triple
T14225462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praga |
E352605
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Nowa Praga |
E352605
|
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: Nowa Praga | Statement: [Praga, hasPart, Nowa Praga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nowa Praga Context triple: [Praga, hasPart, Nowa Praga]
-
A.
Praga
chosen
Praga is a historic district on the eastern bank of the Vistula River in Warsaw, Poland, known for its older architecture, cultural life, and role in the city's wartime history.
-
B.
Prague
Prague is the historic capital city of the Czech Republic, renowned for its well-preserved medieval architecture, iconic Charles Bridge and Prague Castle, and vibrant cultural life.
-
C.
Kolín
Kolín is a historic industrial town and important transport hub on the Elbe River in the Central Bohemian Region of the Czech Republic.
-
D.
Plzeň
Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
-
E.
Prazhskaya
Prazhskaya is a Moscow Metro station named after Prague, featuring Soviet-era architecture with Czech design influences.
- 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_69fd324f501081908f7017302bc40b3a |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:06 a.m.