Triple

T19971568
Position Surface form Disambiguated ID Type / Status
Subject European Games E480087 entity
Predicate abbreviation P43 FINISHED
Object EG 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: EG | Statement: [European Games, abbreviation, EG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EG
Context triple: [European Games, abbreviation, EG]
  • A. EG chosen
    EG is the standard abbreviation for the European Games, a continental multi-sport event for athletes from across Europe.
  • B. EG
    EG is the ISO 3166-1 alpha-2 country code for Egypt, a transcontinental nation in North Africa and the Middle East known for its ancient civilization and monuments like the Pyramids of Giza.
  • C. EG
    EG is the IATA airline code assigned to Enerjet, a Canadian low-cost charter airline.
  • D. EG
    EG is the standard abbreviation for the Egmont Group, an international network of Financial Intelligence Units that collaborates to combat money laundering and terrorist financing.
  • E. GER
    GER is the IATA airport code for Rafael Cabrera Mustelier Airport, which serves Nueva Gerona on Cuba’s Isla de la Juventud.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65bc9694881909a31841702ab9e5f completed April 20, 2026, 5 p.m.
Created at: April 10, 2026, 1:54 p.m.