Triple
T13962643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grześ |
E335834
|
entity |
| Predicate | isNear |
P350
|
FINISHED |
| Object | Wołowiec |
E335835
|
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: Wołowiec | Statement: [Grześ, isNear, Wołowiec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wołowiec Context triple: [Grześ, isNear, Wołowiec]
-
A.
Wołowiec
chosen
Wołowiec is a prominent peak in the Western Tatras on the Polish-Slovak border, popular with hikers for its panoramic views and accessible routes.
-
B.
Wolyniec
Wolyniec is a Polish-origin surname most notably associated with American soccer player and coach John Wolyniec.
-
C.
Wojnicz
Wojnicz is a small historic town in southern Poland, known for its medieval roots and location near the city of Tarnów.
-
D.
Goleniów
Goleniów is a town in northwestern Poland that serves as a local transport hub and gateway to the nearby regional capital Szczecin.
-
E.
Śmielec
Śmielec is a mountain peak in the Karkonosze range of the Sudetes on the border between Poland and the Czech Republic.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7c73d48190b8e02971b5a8ed5f |
completed | April 14, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd27fb2e6c81909e358862e012c49b |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 9, 2026, 10:18 p.m.