Triple

T22789100
Position Surface form Disambiguated ID Type / Status
Subject Livingston North railway station E564058 entity
Predicate hasAbbreviation P43 FINISHED
Object LSN NE NERFINISHED

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: LSN | Statement: [Livingston North railway station, hasAbbreviation, LSN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LSN
Context triple: [Livingston North railway station, hasAbbreviation, LSN]
  • A. LSN chosen
    LSN is the National Rail station code for Livingston North railway station in West Lothian, Scotland.
  • B. LNS
    LNS is the three-letter IATA airport code for Lancaster Airport in Lancaster County, Pennsylvania, serving regional air traffic.
  • C. LNS
    LNS is the commonly used abbreviation for Lindsey Nelson Stadium, the University of Tennessee’s baseball venue in Knoxville.
  • D. LNS
    LNS is the commonly used abbreviation for the Laboratory for Nuclear Science, a research institution focused on advancing the understanding of nuclear and particle physics.
  • E. LTSB
    LTSB is a specialized edition of Windows designed for long-term stability and minimal feature changes, primarily used in enterprise and mission-critical environments.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2455500788190b4b33030461f3bbd completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17c33be7c8190ad22391a85fa000d completed April 29, 2026, 3:34 a.m.
Created at: April 17, 2026, 3:29 p.m.