Triple

T553313
Position Surface form Disambiguated ID Type / Status
Subject Sporting Kansas City E11887 entity
Predicate nickname P55 FINISHED
Object SKC E69348 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: SKC | Statement: [Sporting Kansas City, nickname, SKC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SKC
Context triple: [Sporting Kansas City, nickname, SKC]
  • A. SKC chosen
    SKC is the commonly used abbreviation for Sporting Kansas City, a professional Major League Soccer club based in Kansas City.
  • B. SK
    SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
  • C. SKK
    SKK was the ISO 4217 currency code for the Slovak koruna, the former official currency of Slovakia before adoption of the euro.
  • D. Sk
    Sk is the currency symbol that was used to denote the Slovak koruna, the former national currency of Slovakia before adoption of the euro.
  • E. SKBO
    SKBO is the ICAO airport code for El Dorado International Airport, the main international gateway serving Bogotá, Colombia.
  • 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_69a4932941d08190815efd422f0b4ca7 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4991b296481908cf27e1d1ec67052 completed March 1, 2026, 7:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4e632e7c48190b211f7fcc4903dea completed March 2, 2026, 1:21 a.m.
Created at: March 1, 2026, 7:32 p.m.