Triple

T5118083
Position Surface form Disambiguated ID Type / Status
Subject Jabalpur Airport E115386 entity
Predicate IATAcode P418 FINISHED
Object JLR E481685 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: JLR | Statement: [Jabalpur Airport, IATAcode, JLR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: JLR
Context triple: [Jabalpur Airport, IATAcode, JLR]
  • A. JLR chosen
    JLR is the IATA airport code for Dumna Airport, which serves the city of Jabalpur in the Indian state of Madhya Pradesh.
  • B. Jaguar Land Rover
    Jaguar Land Rover is a British multinational automotive company known for designing and manufacturing luxury vehicles under the Jaguar and Land Rover brands.
  • C. LEVC
    LEVC is the ICAO airport code for Valencia Airport, the main international airport serving the city of Valencia in Spain.
  • D. Bentley
    Bentley is a small village and civil parish in Suffolk, England, known for its rural character and traditional English countryside setting.
  • E. Bentley
    Bentley is a British luxury automobile manufacturer renowned for its high-performance grand tourers and handcrafted interiors.
  • 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_69bd4442ade0819087b9461f892b206b completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd77ce1ea48190b283cae7bb9b72eb completed March 20, 2026, 4:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69bec4a6a7988190b9beec3f0d9494d1 completed March 21, 2026, 4:17 p.m.
Created at: March 20, 2026, 1:41 p.m.