Triple
T905150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plzeň |
E19529
|
entity |
| Predicate | demonym |
P191
|
FINISHED |
| Object | Plzeňan |
E19529
|
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: Plzeňan | Statement: [Plzeň, demonym, Plzeňan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plzeňan Context triple: [Plzeň, demonym, Plzeňan]
-
A.
Plzeň
chosen
Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
-
B.
Ruzinov
Ružinov is a borough of Bratislava, Slovakia, known as a major residential and commercial district of the capital.
-
C.
Zlín
Zlín is a city in the Czech Republic known for its modernist architecture and historical association with the Baťa shoe company.
-
D.
Ostrava
Ostrava is a major industrial and cultural city in the northeastern Czech Republic, near the borders with Poland and Slovakia.
-
E.
Hradec Králové
Hradec Králové is a historic city in the Czech Republic known for its educational institutions, modernist architecture, and role as a regional cultural and economic center.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2caf4088190ab05b22531ecec43 |
completed | March 1, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7c7391e6c8190836e8d7e7fdf9c93 |
completed | March 4, 2026, 5:46 a.m. |
Created at: March 1, 2026, 7:39 p.m.