Triple

T9047335
Position Surface form Disambiguated ID Type / Status
Subject Rotor Volgograd E216787 entity
Predicate foundedAs P364 FINISHED
Object Traktor Stalingrad E216781 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: Traktor Stalingrad | Statement: [Rotor Volgograd, foundedAs, Traktor Stalingrad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Traktor Stalingrad
Context triple: [Rotor Volgograd, foundedAs, Traktor Stalingrad]
  • A. Traktor Stalingrad chosen
    Traktor Stalingrad was a Soviet-era football club from the city then known as Stalingrad, later renamed FC Rotor Volgograd.
  • B. Traktor Chelyabinsk
    Traktor Chelyabinsk is a professional ice hockey club from Chelyabinsk, Russia, historically recognized as one of the prominent teams in Soviet and Russian hockey.
  • C. T-10
    T-10 is the station code for Nihonbashi Station on Tokyo Metro’s Tozai Line in central Tokyo.
  • D. T-80 tank
    The T-80 tank is a Soviet-era main battle tank notable for being one of the first production tanks powered by a gas turbine engine, combining high mobility with heavy armor and firepower.
  • E. KV-1 heavy tank
    The KV-1 heavy tank was a Soviet World War II armored vehicle noted for its exceptionally thick armor and significant role in early Eastern Front battles.
  • 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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc6b5022c88190ab6b6de3c3830a41 completed April 1, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffdb868e48190b9d193025cb5b9a2 completed April 3, 2026, 5:49 p.m.
Created at: March 30, 2026, 7:09 p.m.