Triple
T14428187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Schaffhausen |
E357749
|
entity |
| Predicate | ISO3166-2Code |
P208
|
FINISHED |
| Object | CH-SH |
E568254
|
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: CH-SH | Statement: [canton of Schaffhausen, ISO3166-2Code, CH-SH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CH-SH Context triple: [canton of Schaffhausen, ISO3166-2Code, CH-SH]
-
A.
CH-SH
chosen
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.
-
B.
CH-SO
CH-SO is the ISO 3166-2 code designating the Swiss canton of Solothurn.
-
C.
CH-SG
CH-SG is the ISO 3166-2 code for the Swiss canton of St. Gallen.
-
D.
CHS
CHS is the abbreviation for the Committee on Hemispheric Security, a body within the Organization of American States focused on security issues in the Western Hemisphere.
-
E.
CHS
CHS is the three-letter IATA airport code for Charleston International Airport, the primary commercial airport serving the Charleston, South Carolina area.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91154de881909266ae88d1545685 |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bd1c4d0819085edb9ed22128b68 |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 10, 2026, 1:18 a.m.