Triple

T5457719
Position Surface form Disambiguated ID Type / Status
Subject Sarajevo Olympics 1984 E122519 entity
Predicate skiJumpingVenue P16743 FINISHED
Object Igman E512953 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: Igman | Statement: [Sarajevo Olympics 1984, skiJumpingVenue, Igman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Igman
Context triple: [Sarajevo Olympics 1984, skiJumpingVenue, Igman]
  • A. Igman chosen
    Igman is a mountain in central Bosnia and Herzegovina known for its forests, ski facilities, and role as a key venue during the 1984 Winter Olympics near Sarajevo.
  • B. Oreshak
    Oreshak is a village in central Bulgaria known for its proximity to the historic Troyan Monastery and its traditional crafts and cultural heritage.
  • C. Stryama
    Stryama is a river in Bulgaria that flows through the central part of the country before joining the Maritsa River.
  • D. Taborio
    Taborio is a village settlement located on the island of Nonouti in the Republic of Kiribati.
  • E. Oreshek
    Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
  • 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_69bd46424248819085282ddf50a565f3 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd91f1cca48190afa15b8ccfea1f88 completed March 20, 2026, 6:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf41465c3c8190a58350f39d626e54 completed March 22, 2026, 1:09 a.m.
Created at: March 20, 2026, 2:08 p.m.