Triple
T13222876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Śrem |
E314798
|
entity |
| Predicate | subdivisionName |
P747
|
FINISHED |
| Object | Gmina Śrem |
E314798
|
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 Śrem | Statement: [Gmina Śrem, subdivisionName, Gmina Śrem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Śrem Context triple: [Gmina Śrem, subdivisionName, Gmina Śrem]
-
A.
Gmina Śrem
chosen
Gmina Śrem is an urban-rural administrative district in west-central Poland, centered on the town of Śrem in the Greater Poland Voivodeship.
-
B.
Gmina Gnojno
Gmina Gnojno is a rural administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
-
C.
Gmina Włoszczowa
Gmina Włoszczowa is an administrative district in south-central Poland that includes the town of Włoszczowa and surrounding rural areas.
-
D.
Gmina Secemin
Gmina Secemin is a rural administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
-
E.
Gmina Zembrzyce
Gmina Zembrzyce is a rural administrative district in southern Poland, located in the 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf74d708190a61d8ad938653b06 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716c4a71c8190b0e0ae40af115c64 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:19 p.m.