Triple

T18909141
Position Surface form Disambiguated ID Type / Status
Subject Czech 2. Liga E462550 entity
Predicate sponsor P67 FINISHED
Object Fortuna 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: Fortuna | Statement: [Czech 2. Liga, sponsor, Fortuna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fortuna
Context triple: [Czech 2. Liga, sponsor, Fortuna]
  • A. Fortuna
    Fortuna is a German professional football club based in Düsseldorf, known for its long history and fluctuating presence between the top tiers of German football.
  • B. Fortuna
    Fortuna is a municipality in Spain’s Region of Murcia, known for its thermal baths and natural landscapes.
  • C. Fortuna chosen
    Fortuna is a prominent Central European betting and gaming company known for sponsoring major sports competitions, including top-tier football leagues.
  • D. Fortuna Primigenia
    Fortuna Primigenia was an important ancient Roman goddess of fortune and fate, especially venerated at Praeneste as a powerful oracular deity.
  • E. Tyche
    Tyche is the Greek goddess of fortune, chance, and the prosperity or misfortune of cities and individuals.
  • 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_69d8dcfd05bc819088903cca13cc2846 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c62182f48190ad81b6ef0c7bc7da completed April 20, 2026, 6:22 a.m.
Created at: April 10, 2026, 11:58 a.m.