Triple

T22422128
Position Surface form Disambiguated ID Type / Status
Subject Mitsubishi Regional Jet E554273 entity
Predicate alsoKnownAs P39 FINISHED
Object MRJ 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: MRJ | Statement: [Mitsubishi Regional Jet, alsoKnownAs, MRJ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MRJ
Context triple: [Mitsubishi Regional Jet, alsoKnownAs, MRJ]
  • A. Mitsubishi Regional Jet chosen
    The Mitsubishi Regional Jet is a Japanese-developed family of narrow-body regional jet airliners designed to compete in the 70–90 seat market with improved fuel efficiency and passenger comfort.
  • B. mrj
    mrj is the ISO 639-3 code for Hill Mari, a Uralic language spoken by the Mari people primarily in Russia’s Mari El Republic.
  • C. Mitsubishi CRJ700
    The Mitsubishi CRJ700 is a regional jet airliner designed for short- to medium-haul routes, commonly used by regional carriers around the world.
  • D. MJI
    MJI is the IATA airport code for Mitiga International Airport, a major airport serving Tripoli, Libya.
  • E. Mil Mi-PS
    The Mil Mi-PS is a Soviet-era helicopter variant developed by the Mil design bureau, adapted primarily for search-and-rescue and passenger transport roles.
  • 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_69e11e4f2d0c819091aa3558ea2ee630 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15a2a1a3c8190a649ee4df2429e69 completed April 29, 2026, 1:08 a.m.
Created at: April 16, 2026, 8:47 p.m.