Triple

T5976801
Position Surface form Disambiguated ID Type / Status
Subject Recife/Guararapes–Gilberto Freyre International Airport E133020 entity
Predicate IATAcode P418 FINISHED
Object REC E8667 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: REC | Statement: [Recife/Guararapes–Gilberto Freyre International Airport, IATAcode, REC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: REC
Context triple: [Recife/Guararapes–Gilberto Freyre International Airport, IATAcode, REC]
  • A. REC chosen
    REC is the standard abbreviation used by the World Wide Web Consortium (W3C) to denote a finalized, stable web standard known as a W3C Recommendation.
  • B. REV
    REV is the stock ticker symbol for Revlon Inc., a major American cosmetics, skincare, fragrance, and personal care company.
  • C. RE
    RE is the common abbreviation for the British Army’s Corps of Royal Engineers, responsible for military engineering and technical support.
  • D. RE
    RE is the two-letter ISO 3166-1 alpha-2 country code assigned to the French overseas department and region of Réunion.
  • E. RE
    RE is the abbreviation for RegioExpress, a category of regional express trains commonly used in European rail transport.
  • 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_69c0086f45e8819098f73dd16d45ec9d completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04a3cffb08190a764a404a4ce5812 completed March 22, 2026, 7:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e4184a708190a9e4fe8453463a4b completed March 23, 2026, 6:56 a.m.
Created at: March 22, 2026, 4:04 p.m.