Triple

T12311414
Position Surface form Disambiguated ID Type / Status
Subject Krestovsky Stadium E293486 entity
Predicate namedAfter P63 FINISHED
Object Gazprom E282855 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: Gazprom | Statement: [Krestovsky Stadium, namedAfter, Gazprom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gazprom
Context triple: [Krestovsky Stadium, namedAfter, Gazprom]
  • A. Gazprom chosen
    Gazprom is a Russian state-controlled energy giant and one of the world’s largest producers and exporters of natural gas.
  • B. Rosneft
    Rosneft is a major Russian state-controlled oil company and one of the world’s largest publicly traded petroleum producers.
  • C. Gazprom Neft
    Gazprom Neft is a major Russian oil company engaged in exploration, production, refining, and marketing of petroleum products.
  • D. Gazprom Transgaz
    Gazprom Transgaz is a major Russian gas transmission company responsible for operating and maintaining large sections of Gazprom’s natural gas pipeline network.
  • E. Rosneftegaz
    Rosneftegaz is a Russian state-owned holding company that historically managed the government’s stakes in major oil and gas enterprises, including what became Rosneft.
  • 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_69d6ab6a2b50819082f6aedd32ed608a completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f02c0508190b10c0627cdaaba76 completed April 10, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62a9d50b081908f0bdb7a2ca2832a completed May 2, 2026, 4:47 p.m.
Created at: April 8, 2026, 9:53 p.m.