Triple
T19266069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bujaków |
E481780
|
entity |
| Predicate | isNowPartOf |
P74112
|
FINISHED |
| Object | town of Mikołów |
—
|
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: town of Mikołów | Statement: [Bujaków, isNowPartOf, town of Mikołów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: town of Mikołów Context triple: [Bujaków, isNowPartOf, town of Mikołów]
-
A.
Mikołów
chosen
Mikołów is a historic town in southern Poland known for its traditional Silesian character and proximity to the regional capital, Katowice.
-
B.
town of Polańczyk
The town of Polańczyk is a popular spa and tourist resort in southeastern Poland, known for its scenic location in the Bieszczady region and its health resorts and lakeside recreation.
-
C.
Michałów
Michałów is a village and the seat of a rural administrative district (gmina) in south-central Poland.
-
D.
Michałów
Michałów is a village in east-central Poland located within the administrative district of Gmina Leoncin in the Masovian Voivodeship.
-
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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8d58988190a942627b1fb79285 |
completed | April 20, 2026, 10:10 a.m. |
Created at: April 10, 2026, 1:29 p.m.