Triple

T17784758
Position Surface form Disambiguated ID Type / Status
Subject Grabs E443988 entity
Predicate hasISO3166-2Code P208 FINISHED
Object CH-SG 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: CH-SG | Statement: [Grabs, hasISO3166-2Code, CH-SG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CH-SG
Context triple: [Grabs, hasISO3166-2Code, CH-SG]
  • A. CH-SG chosen
    CH-SG is the ISO 3166-2 code for the Swiss canton of St. Gallen.
  • B. CH-SO
    CH-SO is the ISO 3166-2 code designating the Swiss canton of Solothurn.
  • C. CH-SZ
    CH-SZ is the ISO 3166-2 code for the Swiss canton of Schwyz, a central canton known as one of the founding members of the Swiss Confederation.
  • D. CH-SH
    CH-SH is the Swiss canton of Schaffhausen, a small German-speaking region in northern Switzerland known for its historic old town and the nearby Rhine Falls.
  • E. CH-BS
    CH-BS is the ISO 3166-2 code for the Swiss canton of Basel-Stadt, an urban canton centered on the city of Basel.
  • 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_69d8b9ef17708190bdf7e2adbf14ddc2 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48791dec0819090d6e88449389fc0 completed April 19, 2026, 7:43 a.m.
Created at: April 10, 2026, 10:12 a.m.