Triple
T23132566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ustroń |
E577212
|
entity |
| Predicate | hasDistrict |
P459
|
FINISHED |
| Object | Ustroń Jelenica |
—
|
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: Ustroń Jelenica | Statement: [Ustroń, hasDistrict, Ustroń Jelenica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ustroń Jelenica Context triple: [Ustroń, hasDistrict, Ustroń Jelenica]
-
A.
Oleśnica
Oleśnica is a village located in Busko County in the Świętokrzyskie Voivodeship of south-central Poland.
-
B.
Oleśnica
Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
-
C.
Ustroń
chosen
Ustroń is a spa town in southern Poland’s Silesian Beskids, known for its health resorts, mountain tourism, and role as a gateway to popular hiking routes.
-
D.
Ustrzyki Górne
Ustrzyki Górne is a small mountain village in southeastern Poland that serves as a key tourist base and hiking gateway to the Bieszczady Mountains.
-
E.
Łęczna
Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e88909881908c695cd7d39d380c |
completed | April 29, 2026, 4:52 a.m. |
Created at: April 17, 2026, 4 p.m.