Triple
T3007820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maków Beskids |
E81943
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Mędralowa |
E317992
|
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: Mędralowa | Statement: [Maków Beskids, hasPeak, Mędralowa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mędralowa Context triple: [Maków Beskids, hasPeak, Mędralowa]
-
A.
Mędralowa
chosen
Mędralowa is a mountain peak in southern Poland that forms the highest summit of the Maków Beskids range.
-
B.
Mława
Mława is a town in north-central Poland known for its historical significance, including a major World War II battle, and its regional cultural and economic role.
-
C.
Muszyna
Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
-
D.
Skawina
Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
-
E.
Słupia
Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4a12508190a48ae1c86233d25e |
completed | March 8, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1dea6b460819087d7186efc901ef2 |
completed | March 11, 2026, 9:29 p.m. |
Created at: March 8, 2026, 3 p.m.