Triple

T3565372
Position Surface form Disambiguated ID Type / Status
Subject Monroe Regional Airport E75434 entity
Predicate FAAcode P420 FINISHED
Object MLU E369376 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: MLU | Statement: [Monroe Regional Airport, FAAcode, MLU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MLU
Context triple: [Monroe Regional Airport, FAAcode, MLU]
  • A. MLU chosen
    MLU is the IATA airport code for Monroe Regional Airport, a public airport serving Monroe, Louisiana, in the United States.
  • B. MML
    MML is a major inter-city rail route in England connecting London with key cities in the East Midlands and South Yorkshire.
  • C. LM
    LM is the IATA airline designator assigned to Loganair, a regional airline based in Scotland.
  • D. LM
    LM is the Apollo Lunar Module, the spacecraft used by NASA during the Apollo program to land astronauts on the Moon and return them to lunar orbit.
  • E. ML
    ML is a post-nominal honorific indicating a recipient of Papua New Guinea’s Order of Logohu, a national order of merit.
  • 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_69ad85d512708190829c8b2d3a2ccfb8 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc0a8f6288190928479f5bea32245 completed March 8, 2026, 6:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69b402e8628c81909913974602782b7a completed March 13, 2026, 12:28 p.m.
Created at: March 8, 2026, 3:21 p.m.