Triple
T17531662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirosław |
E426949
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Mirosławek |
—
|
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: Mirosławek | Statement: [Mirosław, relatedName, Mirosławek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mirosławek Context triple: [Mirosław, relatedName, Mirosławek]
-
A.
Mirosław
chosen
Mirosław is a Polish masculine given name, equivalent to the Slavic name Miroslav.
-
B.
Mikołów
Mikołów is a historic town in southern Poland known for its traditional Silesian character and proximity to the regional capital, Katowice.
-
C.
Miłosław
Miłosław is a historic town in west-central Poland known for its role in the 1848 Greater Poland Uprising against Prussian rule.
-
D.
Muszyna
Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
-
E.
Miłków
Miłków is a village in southwestern Poland situated in the scenic Jelenia Góra Valley near the Karkonosze Mountains.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e453695734819092d4dcbab4a4fa01 |
completed | April 19, 2026, 4 a.m. |
Created at: April 10, 2026, 5:49 a.m.