Triple
T13347319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Jordanów |
E317985
|
entity |
| Predicate | subdivisionName |
P747
|
FINISHED |
| Object | Gmina Jordanów |
E317985
|
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 Jordanów | Statement: [Gmina Jordanów, subdivisionName, Gmina Jordanów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Jordanów Context triple: [Gmina Jordanów, subdivisionName, Gmina Jordanów]
-
A.
Gmina Jordanów
chosen
Gmina Jordanów is an administrative district in southern Poland, located in the Lesser Poland Voivodeship and centered around the town of Jordanów.
-
B.
Gmina Ojrzeń
Gmina Ojrzeń is a rural administrative district in east-central Poland, situated within the Masovian Voivodeship.
-
C.
Gmina Jędrzejów
Gmina Jędrzejów is an administrative district (gmina) in south-central Poland, centered on the town of Jędrzejów in the Świętokrzyskie Voivodeship.
-
D.
Gmina Jeziorany
Gmina Jeziorany is an administrative district (gmina) in northern Poland centered around the town of Jeziorany.
-
E.
Gmina Gródek
Gmina Gródek is a rural administrative district in north-eastern Poland, known for its forests, borderland location near Belarus, and multicultural heritage.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e89c65c819093f3bea11d6073c5 |
completed | April 11, 2026, 1:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f45c9788190b60095c0d6e2f763 |
completed | May 3, 2026, 10:11 a.m. |
Created at: April 9, 2026, 9:31 p.m.