Triple

T11942339
Position Surface form Disambiguated ID Type / Status
Subject São Paulo–Guarulhos International Airport E284206 entity
Predicate ICAOCode P419 FINISHED
Object SBGR E284206 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: SBGR | Statement: [São Paulo–Guarulhos International Airport, ICAOCode, SBGR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SBGR
Context triple: [São Paulo–Guarulhos International Airport, ICAOCode, SBGR]
  • A. SBGR chosen
    SBGR is the ICAO airport code for São Paulo–Guarulhos International Airport, the main international gateway serving São Paulo, Brazil.
  • B. SBGL
    SBGL is the ICAO airport code for Rio de Janeiro–Galeão International Airport, a major international gateway serving Rio de Janeiro, Brazil.
  • C. BRG
    BRG is the stock ticker symbol for Borregaard, a Norwegian company specializing in advanced and sustainable biochemicals derived from wood.
  • D. SGB
    SGB is the National Rail station code for Smethwick Galton Bridge railway station in the West Midlands, England.
  • E. SBGI
    SBGI is the stock ticker symbol for Sinclair Broadcast Group, a major American telecommunications company and television station owner.
  • 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90342bb908190a019ac91a2b82f3d completed April 10, 2026, 2:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69f440a5a9c8819086a94ad60c6881b8 completed May 1, 2026, 5:56 a.m.
Created at: April 8, 2026, 9:45 p.m.