Triple
T7686957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trzy Korony massif |
E174141
|
entity |
| Predicate | hasPeak |
P8205
|
FINISHED |
| Object | Pańska Skała |
E681702
|
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: Pańska Skała | Statement: [Trzy Korony massif, hasPeak, Pańska Skała]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pańska Skała Context triple: [Trzy Korony massif, hasPeak, Pańska Skała]
-
A.
Malinowska Skała
Malinowska Skała is a notable mountain peak in southern Poland, situated within the Silesian Beskids range and popular for its hiking trails and scenic views.
-
B.
Pieskowa Skała
Pieskowa Skała is a historic Renaissance castle in southern Poland, picturesquely situated in the Ojców National Park within the Prądnik River valley.
-
C.
Szklarska Poręba
Szklarska Poręba is a popular Polish mountain resort town known for skiing, hiking, and scenic landscapes in the Karkonosze range near the Czech border.
-
D.
Płaska Skała
chosen
Płaska Skała is one of the notable peaks within the Trzy Korony massif in the Pieniny Mountains of southern Poland.
-
E.
Skała
Skała is a small historic town in southern Poland, located near Kraków and known as a gateway to the scenic Ojców National Park.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7022352088190b2510d5fac55864f |
completed | March 27, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8aca0b5b08190b178f0908612164c |
completed | March 29, 2026, 4:37 a.m. |
Created at: March 27, 2026, 4:02 p.m.