Triple

T21586309
Position Surface form Disambiguated ID Type / Status
Subject Lesyk E532659 entity
Predicate relatedName P3889 FINISHED
Object Lesko NE NERFINISHED

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: Lesko | Statement: [Lesyk, relatedName, Lesko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lesko
Context triple: [Lesyk, relatedName, Lesko]
  • A. Lesko chosen
    Lesko is a small town in southeastern Poland, often considered a gateway to the Bieszczady Mountains and known for its historic architecture and scenic surroundings.
  • B. Olesko
    Olesko is a historic town in western Ukraine best known for its medieval castle, which served as the birthplace of Polish King John III Sobieski.
  • C. Klier
    Klier is a surname of German origin borne by various notable individuals across fields such as sports, arts, and academia.
  • D. Lembeck
    Lembeck is a surname most notably associated with American actor and comedian Harvey Lembeck.
  • E. Mahlberg
    Mahlberg is a small town and municipality in the Ortenau district of Baden-Württemberg in southwestern Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46251648190876f0427cf2d321b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeeb6137fc8190840b7c1275e62a1d completed April 27, 2026, 4:51 a.m.
Created at: April 16, 2026, 6:31 p.m.