Triple

T14551002
Position Surface form Disambiguated ID Type / Status
Subject Stade de Genève E341416 entity
Predicate tenant P75 FINISHED
Object Servette FC E561757 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: Servette FC | Statement: [Stade de Genève, tenant, Servette FC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Servette FC
Context triple: [Stade de Genève, tenant, Servette FC]
  • A. Servette FC chosen
    Servette FC is a historic professional football club from Geneva, Switzerland, known as one of the country’s most successful and traditional teams.
  • B. FC Sion
    FC Sion is a Swiss professional football club from Sion, best known for its strong domestic cup tradition and passionate fan base.
  • C. Yverdon-Sport FC
    Yverdon-Sport FC is a Swiss professional football club based in Yverdon-les-Bains that competes in the country’s league system.
  • D. FC Stade Nyonnais
    FC Stade Nyonnais is a Swiss football club based in the town of Nyon that competes in the national league system.
  • E. FC Lausanne-Sport
    FC Lausanne-Sport is a Swiss professional football club based in Lausanne that competes in the country’s top leagues and has a long-standing presence in national competitions.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2ee34208190bf040a513767c958 completed April 14, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8ab5d50881908f53f8b7539c6fde completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:23 a.m.