Triple
T12740507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciechanów County |
E304475
|
entity |
| Predicate | containsRuralGmina |
P46876
|
FINISHED |
| Object | Gmina Regimin |
E1001204
|
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 Regimin | Statement: [Ciechanów County, containsRuralGmina, Gmina Regimin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Regimin Context triple: [Ciechanów County, containsRuralGmina, Gmina Regimin]
-
A.
Gmina Regimin
chosen
Gmina Regimin is a rural administrative district in east-central Poland, located in the Masovian Voivodeship.
-
B.
Gmina Gorlice
Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
-
C.
Gmina Trzebinia
Gmina Trzebinia is an urban-rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
-
D.
Gmina Rytro
Gmina Rytro is a rural administrative district in southern Poland, situated in the Lesser Poland Voivodeship and known for its mountainous landscapes in the Beskid Sądecki range.
-
E.
Gmina Drwinia
Gmina Drwinia 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96facb2d48190bc12efc00c9da360 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684eba2508190966d084cc21dc1ea |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:26 p.m.