Triple

T370666
Position Surface form Disambiguated ID Type / Status
Subject San Diego E8261 entity
Predicate airportIATA P418 FINISHED
Object SAN E32609 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: SAN | Statement: [San Diego, airportIATA, SAN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SAN
Context triple: [San Diego, airportIATA, SAN]
  • A. SAN chosen
    SAN is the three-letter IATA airport code for San Diego International Airport, the primary commercial airport serving the San Diego, California area.
  • B. SA
    SA is a key 3GPP technical specification group responsible for defining the overall system architecture and service capabilities of mobile telecommunications networks.
  • C. SA
    The SA (Sturmabteilung) was the Nazi Party’s paramilitary organization known for its role in Adolf Hitler’s rise to power through intimidation, street violence, and mass rallies in early 20th-century Germany.
  • D. SA
    SA is the two-letter ISO 3166-1 alpha-2 country code representing the Kingdom of Saudi Arabia.
  • E. NAS
    NAS is a private, nonprofit society of distinguished scholars in the United States that advises the nation on matters related to science and technology.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebff472881909fad81d597425ea6 completed Feb. 28, 2026, 1:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3ecac7e048190a76c02c738599c61 completed March 1, 2026, 7:37 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.