Triple

T2125775
Position Surface form Disambiguated ID Type / Status
Subject RAEng E46421 entity
Predicate hasAbbreviation P43 FINISHED
Object RAEng E46421 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: RAEng | Statement: [RAEng, hasAbbreviation, RAEng]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RAEng
Context triple: [RAEng, hasAbbreviation, RAEng]
  • A. RAEng chosen
    RAEng is the commonly used abbreviation for the Royal Academy of Engineering, the United Kingdom’s national academy for engineering and technology.
  • B. ENGM
    ENGM is the ICAO airport code for Oslo Airport, Gardermoen, the main international airport serving Norway’s capital region.
  • C. RAE
    RAE is the commonly used acronym for the Royal Spanish Academy, the official institution responsible for regulating and overseeing the Spanish language.
  • D. Engineering Index
    Engineering Index was an early comprehensive bibliographic database that indexed worldwide engineering and technical literature, later evolving into what is now known as Ei Compendex.
  • E. RJA
    RJA is the ICAO airline designator used for Royal Jordanian, the flag carrier airline of Jordan.
  • 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_69a88a1626548190ae59a5028c3baa8e completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbb57bc6881909f04a407beff33a6 completed March 7, 2026, 5:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae58cf2a588190a59dc1ae5d684538 completed March 9, 2026, 5:21 a.m.
Created at: March 4, 2026, 7:44 p.m.