Triple

T19172966
Position Surface form Disambiguated ID Type / Status
Subject Firozpur Cantonment railway station E469370 entity
Predicate hasStationCode P1289 FINISHED
Object FZR E1354422 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: FZR | Statement: [Firozpur Cantonment railway station, hasStationCode, FZR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FZR
Context triple: [Firozpur Cantonment railway station, hasStationCode, FZR]
  • A. FZR chosen
    FZR is the station and division code used by Indian Railways for the Firozpur railway division in the Northern Railway zone.
  • B. FJR
    FJR is the IATA airport code for Fujairah International Airport in the United Arab Emirates.
  • C. Yamaha FZ series
    The Yamaha FZ series is a popular line of sporty standard motorcycles known for their agile handling, aggressive styling, and strong performance in the middleweight segment.
  • D. FZ
    FZ is the vehicle registration code assigned to cars registered in the city of Zielona Góra in western Poland.
  • E. FZ
    FZ is the IATA airline designator assigned to flydubai, the low-cost carrier based in Dubai, United Arab Emirates.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f16544948190bd10ca7804dd27a5 completed April 20, 2026, 9:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a06f8ae89dc819098830e25b3552dee completed May 15, 2026, 10:42 a.m.
Created at: April 10, 2026, 12:06 p.m.