Triple

T13452899
Position Surface form Disambiguated ID Type / Status
Subject Samastipur E311154 entity
Predicate railwayStationCode P1289 FINISHED
Object SPJ E986670 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: SPJ | Statement: [Samastipur, railwayStationCode, SPJ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SPJ
Context triple: [Samastipur, railwayStationCode, SPJ]
  • A. SPJ chosen
    SPJ is the Indian Railways station code for Samastipur Junction, a major railway hub in the state of Bihar.
  • B. SPJL
    SPJL is the ICAO airport code for Inca Manco Cápac International Airport, which serves the city of Juliaca in southern Peru.
  • C. Society of Professional Journalists
    The Society of Professional Journalists is a major U.S.-based professional organization dedicated to promoting ethical journalism, defending press freedom, and supporting journalists through advocacy, training, and recognition.
  • D. SPJC
    SPJC is the ICAO airport code for Jorge Chávez International Airport, the main international gateway serving Lima, Peru.
  • E. SP&S
    SP&S is the common abbreviation for the Spokane, Portland and Seattle Railway, a historic Pacific Northwest railroad that operated in the United States during the 20th century.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaefae85481909e6a59797cbb25e7 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7399c539c819080802b620da6fcfc completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:41 p.m.