Triple
T6089164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorlice town hall |
E135717
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Gorlice |
E25217
|
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: Gorlice | Statement: [Gorlice town hall, locatedIn, Gorlice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gorlice Context triple: [Gorlice town hall, locatedIn, Gorlice]
-
A.
Gorlice
chosen
Gorlice is a historic town in southern Poland known for its role in the World War I Battle of Gorlice–Tarnów and its early oil industry.
-
B.
Kraśnik
Kraśnik is a town in eastern Poland known for its historical architecture and location within the Lublin region.
-
C.
Czorsztyn
Czorsztyn is a small village in southern Poland known for its picturesque lakeside setting on the Dunajec River and the ruins of a medieval castle overlooking the Pieniny Mountains.
-
D.
Hrubieszów
Hrubieszów is a historic town in eastern Poland near the Ukrainian border, known for its multicultural heritage and location in the Lublin region.
-
E.
Tarnobrzeg
Tarnobrzeg is a city in southeastern Poland known historically for its sulfur mining industry and location along the Vistula River.
- 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_69c20d4e28b48190bb44675c5c035bd3 |
completed | March 24, 2026, 4:04 a.m. |
Created at: March 22, 2026, 4:12 p.m.