Triple

T4002184
Position Surface form Disambiguated ID Type / Status
Subject Streitkräftebasis E89438 entity
Predicate hasAbbreviation P43 FINISHED
Object SKB E407236 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: SKB | Statement: [Streitkräftebasis, hasAbbreviation, SKB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SKB
Context triple: [Streitkräftebasis, hasAbbreviation, SKB]
  • A. SKB chosen
    SKB is the German Bundeswehr’s Joint Support Service, responsible for providing cross-branch logistical, administrative, and operational support to the armed forces.
  • B. SKC
    SKC is the commonly used abbreviation for Sporting Kansas City, a professional Major League Soccer club based in Kansas City.
  • C. SKBO
    SKBO is the ICAO airport code for El Dorado International Airport, the main international gateway serving Bogotá, Colombia.
  • D. SK
    SK is the vehicle registration code used on license plates for vehicles registered in Skopje, the capital city of North Macedonia.
  • E. SK
    SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
  • 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_69aed9585e788190bec2d39deba3750f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefa44125881909f45ecd0a986c581 completed March 9, 2026, 4:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5562455a0819097fb6a566f2d387a completed March 14, 2026, 12:35 p.m.
Created at: March 9, 2026, 3:34 p.m.