Triple
T13521816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleśnica Piasts |
E322915
|
entity |
| Predicate | associatedCity |
P3207
|
FINISHED |
| Object | Oleśnica |
—
|
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: Oleśnica | Statement: [Oleśnica Piasts, associatedCity, Oleśnica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oleśnica Context triple: [Oleśnica Piasts, associatedCity, Oleśnica]
-
A.
Oleśnica
chosen
Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
-
B.
Oleśnica
Oleśnica is a village located in Busko County in the Świętokrzyskie Voivodeship of south-central Poland.
-
C.
Ojców
Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
-
D.
Olsztynek
Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
-
E.
Chojnice
Chojnice is a historic town in northern Poland known for its medieval architecture and role as a local cultural and economic 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa3df0c8190804174695587f0ea |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:44 p.m.