Triple

T22722115
Position Surface form Disambiguated ID Type / Status
Subject Frisco Lines E561888 entity
Predicate abbreviation P43 FINISHED
Object SLSF 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: SLSF | Statement: [Frisco Lines, abbreviation, SLSF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SLSF
Context triple: [Frisco Lines, abbreviation, SLSF]
  • A. SLSF chosen
    SLSF was the reporting mark used by the St. Louis–San Francisco Railway, commonly known as the Frisco, a major Midwestern and Southern U.S. railroad.
  • B. SLF
    SLF is the Shuttle Landing Facility at NASA’s Kennedy Space Center, a specialized runway complex built for landing Space Shuttle orbiters and other aerospace vehicles.
  • C. SLS
    SLS is the vehicle registration code used on license plates for vehicles registered in Saarlouis, Germany.
  • D. SLS
    SLS is a Finnish scholarly society dedicated to the preservation, research, and promotion of Swedish-language literature and cultural heritage in Finland.
  • E. SLS
    SLS is the common abbreviation for the Shiga Lakestars, a professional basketball team based in Shiga Prefecture, Japan.
  • 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17926ae0c8190af8493cab6b15261 completed April 29, 2026, 3:21 a.m.
Created at: April 17, 2026, 3:20 p.m.