Triple

T20614947
Position Surface form Disambiguated ID Type / Status
Subject São Paulo to Frankfurt E506541 entity
Predicate departureAirportIATA P45614 FINISHED
Object GRU 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: GRU | Statement: [São Paulo to Frankfurt, departureAirportIATA, GRU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GRU
Context triple: [São Paulo to Frankfurt, departureAirportIATA, GRU]
  • A. GRU
    GRU is Russia’s military intelligence agency, known for conducting espionage, cyber operations, and covert activities abroad.
  • B. GRU chosen
    GRU is the IATA airport code for São Paulo–Guarulhos International Airport, the main international gateway serving São Paulo, Brazil.
  • C. GRU
    GRU is the abbreviation for the Georgian Rugby Union, the governing body responsible for overseeing and developing rugby union in Georgia.
  • D. RBM
    RBM is a global partnership initiative dedicated to coordinating and scaling up efforts to prevent, control, and ultimately eliminate malaria worldwide.
  • E. NN
    NN is the postcode area in the United Kingdom that covers Northampton and surrounding parts of Northamptonshire.
  • 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_69e0b4bc90988190ac360aaf645efc1d completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aadaf47881909e93efb535c6c1e3 completed April 20, 2026, 10:38 p.m.
Created at: April 16, 2026, 11:41 a.m.