Triple

T22569321
Position Surface form Disambiguated ID Type / Status
Subject Mongolian Football Federation E558036 entity
Predicate usesAbbreviation P43 FINISHED
Object MFF 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: MFF | Statement: [Mongolian Football Federation, usesAbbreviation, MFF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MFF
Context triple: [Mongolian Football Federation, usesAbbreviation, MFF]
  • A. MFF chosen
    MFF is the commonly used abbreviation for the Mongolian Football Federation, the governing body of football in Mongolia.
  • B. MFF
    MFF is the European Union’s long-term budget plan that sets annual spending limits and priorities over a multi-year period.
  • C. MFF
    MFF is the commonly used abbreviation for Malmö FF, a prominent Swedish professional football club based in Malmö.
  • D. MFF UK
    MFF UK is the Faculty of Mathematics and Physics at Charles University in Prague, renowned for its research and education in mathematics, physics, and computer science.
  • E. MFF Support
    MFF Support is the official supporters’ association of Swedish football club Malmö FF, organizing and representing the club’s fan base.
  • 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_69e11e5ae4ac8190b1f503457603d969 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15fac7db08190ba4660535571498d completed April 29, 2026, 1:32 a.m.
Created at: April 16, 2026, 8:52 p.m.