Triple
T17328531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stary Korczyn |
E420751
|
entity |
| Predicate | locatedInAdministrativeUnit |
P40
|
FINISHED |
| Object | Gmina Nowy Korczyn |
E565905
|
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: Gmina Nowy Korczyn | Statement: [Stary Korczyn, locatedInAdministrativeUnit, Gmina Nowy Korczyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Nowy Korczyn Context triple: [Stary Korczyn, locatedInAdministrativeUnit, Gmina Nowy Korczyn]
-
A.
Gmina Nowy Korczyn
chosen
Gmina Nowy Korczyn is a rural administrative district in south-central Poland, located in the Świętokrzyskie Voivodeship.
-
B.
Gmina Korzenna
Gmina Korzenna is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
-
C.
Gmina Korsze
Gmina Korsze is an administrative district (gmina) in northern Poland that encompasses the town of Korsze and surrounding villages.
-
D.
Gmina Nowy Sącz
Gmina Nowy Sącz is an urban administrative district in southern Poland that encompasses the city of Nowy Sącz and manages its local government affairs.
-
E.
Nowy Korczyn
Nowy Korczyn is a historic town in south-central Poland, located in the Świętokrzyskie 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d42154819093a240f677a63145 |
completed | April 19, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c4dff088190833122dbe2981045 |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:43 a.m.