Triple

T10202610
Position Surface form Disambiguated ID Type / Status
Subject Quad Cities International Airport E238918 entity
Predicate FAAcode P420 FINISHED
Object MLI E847571 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: MLI | Statement: [Quad Cities International Airport, FAAcode, MLI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MLI
Context triple: [Quad Cities International Airport, FAAcode, MLI]
  • A. MLI
    MLI is the three-letter ISO 3166-1 alpha-3 country code assigned to Mali.
  • B. MLI chosen
    MLI is the IATA airport code for Quad Cities International Airport serving the Quad Cities region in Illinois and Iowa, United States.
  • C. ML-2
    ML-2 is a major north–south railway corridor in Pakistan that serves as one of the country’s principal main lines parallel to the primary ML-1 route.
  • D. ML-1
    ML-1 is Pakistan Railways’ primary north–south main line, connecting major cities and serving as the backbone of the country’s rail transport system.
  • E. MSL
    MSL is a NASA mission featuring the Curiosity rover, designed to explore Mars’ surface and assess its past and present habitability.
  • 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_69ca84e1ea088190b38162e43d4cfa8f completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdee4239c08190b40f5cc19c3db3c7 completed April 2, 2026, 4:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d32afa75ec8190bbaf2e69b4ee24f1 completed April 6, 2026, 3:39 a.m.
Created at: March 30, 2026, 9:14 p.m.