Triple

T9536726
Position Surface form Disambiguated ID Type / Status
Subject Zimbabwe national football team E230036 entity
Predicate fifaTrigramme P6278 FINISHED
Object ZIM E544842 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: ZIM | Statement: [Zimbabwe national football team, fifaTrigramme, ZIM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ZIM
Context triple: [Zimbabwe national football team, fifaTrigramme, ZIM]
  • A. ZIM chosen
    ZIM is the official International Cricket Council country code used to represent the Zimbabwe national cricket team in international cricket.
  • B. ZMB
    ZMB is the three-letter ISO 3166-1 alpha-3 country code assigned to Zambia.
  • C. Zvimba
    Zvimba is a town in northern Zimbabwe located within Mashonaland West Province, known primarily as a rural administrative and farming center.
  • D. Zemba
    Zemba is a Bantu language variety spoken primarily in southwestern Angola and northern Namibia, closely related to and often considered a dialect of Herero.
  • E. TZA
    TZA is the IATA airport code for Belize City Municipal Airport, a domestic airport serving Belize City in Belize.
  • 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_69ca847b1b3081908f72bc932c17cc41 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98ce884c8190a8b3c2dc7c73c2c9 completed April 1, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69d14c4f1fc08190a1ad3d862717eef3 completed April 4, 2026, 5:37 p.m.
Created at: March 30, 2026, 8:01 p.m.