Triple
T6763841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatra County |
E154663
|
entity |
| Predicate | hasMajorVillage |
P2321
|
FINISHED |
| Object | Białka Tatrzańska |
E98231
|
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: Białka Tatrzańska | Statement: [Tatra County, hasMajorVillage, Białka Tatrzańska]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Białka Tatrzańska Context triple: [Tatra County, hasMajorVillage, Białka Tatrzańska]
-
A.
Białka Tatrzańska
chosen
Białka Tatrzańska is a popular mountain village and ski resort in southern Poland, known for its thermal baths and access to the Tatra Mountains.
-
B.
Sokółka
Sokółka is a small town in northeastern Poland known for its location in the Podlasie region near the border with Belarus.
-
C.
Słomniki
Słomniki is a small town in southern Poland, located in the Lesser Poland Voivodeship.
-
D.
Świątniki Górne
Świątniki Górne is a small town in southern Poland, situated near Kraków and known for its traditional locksmithing and metalworking industries.
-
E.
Szerzyny
Szerzyny is a village in southern Poland located within the administrative region of Lesser Poland Voivodeship.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d217bbfc81908c9e55efaf7f8594 |
completed | March 27, 2026, 6:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c712b9e7f081909d9fcc219ac525b8 |
completed | March 27, 2026, 11:28 p.m. |
Created at: March 27, 2026, 2:12 p.m.