Triple

T5729060
Position Surface form Disambiguated ID Type / Status
Subject Beskid Wyspowy E126336 entity
Predicate contains P35 FINISHED
Object Mogielica E547278 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: Mogielica | Statement: [Beskid Wyspowy, contains, Mogielica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mogielica
Context triple: [Beskid Wyspowy, contains, Mogielica]
  • A. Mogielica chosen
    Mogielica is a prominent mountain peak in southern Poland, known for its scenic hiking trails and panoramic views of the Beskid Wyspowy range.
  • B. Muszyna
    Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
  • C. 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.
  • D. Ciechocinek
    Ciechocinek is a Polish spa town renowned for its historic saline graduation towers and therapeutic health resorts.
  • E. Milejewo
    Milejewo is a small village in northern Poland, located in the Warmian-Masurian Voivodeship and known for its rural character and surrounding natural landscapes.
  • 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_69c0082f723881908ce8bb13a0c0f8b7 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0250d5f4c8190a36b43ef5e6c7837 completed March 22, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a1605f808190a45359e213354799 completed March 23, 2026, 2:11 a.m.
Created at: March 22, 2026, 3:47 p.m.