Triple
T6089119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Gorlice |
E135715
|
entity |
| Predicate | subdivisionName |
P747
|
FINISHED |
| Object | Gmina Gorlice |
E135715
|
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 Gorlice | Statement: [Gmina Gorlice, subdivisionName, Gmina Gorlice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Gorlice Context triple: [Gmina Gorlice, subdivisionName, Gmina Gorlice]
-
A.
Gmina Gorlice
chosen
Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
-
B.
Gmina Gnojno
Gmina Gnojno is a rural administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
-
C.
Gmina Zawichost
Gmina Zawichost is a rural administrative district in south-eastern Poland, centered on the historic town of Zawichost in the Świętokrzyskie Voivodeship.
-
D.
Gmina Końskie
Gmina Końskie is an administrative district in south-central Poland that includes the town of Końskie and surrounding rural areas within Końskie County.
-
E.
Gmina Górno
Gmina Górno is a rural administrative district 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057a862c88190912a913973c6b6fc |
completed | March 22, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c12531d764819083e1bb37d8c81a6c |
completed | March 23, 2026, 11:34 a.m. |
Created at: March 22, 2026, 4:12 p.m.